-
Notifications
You must be signed in to change notification settings - Fork 768
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
weird behavior of allow_forking for orgs with forking disabled #1136
Comments
I have the same problem...(on organization repository and my personal repository) |
Not much to add to the original issue here. Very much in the same boat, we tried rolling back to an older provider version but that is also giving headaches because of the massive amounts of repositories we manage. |
Same problem for me. This prevents me to create a new repository with terraform because, even when I run plan/apply twice. |
Running into this issue as well. I would expect it to default to false which is the same functionality as the UI. Looking through the API I don't see anywhere that explicitly states that it defaults to true. In fact it doesn't appear to be documented for create -> https://docs.github.com/en/rest/repos/repos#create-an-organization-repository |
Same problem here. |
Sorry about that folks! I've reverted the offending PR and published v4.24.1 with only that change in it. |
Hi there,
Terraform Version
Terraform v1.1.9
Affected Resource(s)
Terraform Configuration Files
Expected Behavior
Actual Behavior
Steps to Reproduce
Organization with forks disabled, private repository, 4.23.0 of provider
then update provider (without adding allow_forking) and apply
but if run apply second time - everything is fine (and state has allow_forking == true, while really forking is disabled)
then if I disable allow_forking explicitly the error returns
output
but again if run apply second time , then everything is fine
References
#1033
@kfcampbell @diogopms
The text was updated successfully, but these errors were encountered: