You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Provider does not attempt to update/create attributes, github_repository_ruleset in this case, when repository is archived.
Actual Behavior
Provider attempts to update/create github_repository_ruleset, failing with 403 received from GitHub API.
Terraform Version
Terraform v1.0.11 on linux_amd64 + provider registry.terraform.io/integrations/github versions matching v6.3.0
Affected Resource(s)
github_repository_ruleset
Terraform Configuration Files
No response
Steps to Reproduce
Create repository with github_team_repository resource. In the next step, set archived = true and apply changes.
Then, try to add github_repository_ruleset.
While it wouldn't be an issue using standalone resources, using these resources within Terraform modules results in pipeline failures.
The workaround is to unarchive affected repositories, roll out changes related to github_repository_ruleset and archive them again. Rather time-consuming process when handling hundreds of repositories.
Debug Output
No response
Panic Output
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Expected Behavior
Provider does not attempt to update/create attributes,
github_repository_ruleset
in this case, when repository is archived.Actual Behavior
Provider attempts to update/create
github_repository_ruleset
, failing with 403 received from GitHub API.Terraform Version
Terraform v1.0.11 on linux_amd64 + provider registry.terraform.io/integrations/github versions matching v6.3.0
Affected Resource(s)
Terraform Configuration Files
No response
Steps to Reproduce
Create repository with
github_team_repository
resource. In the next step, setarchived = true
and apply changes.Then, try to add
github_repository_ruleset
.While it wouldn't be an issue using standalone resources, using these resources within Terraform modules results in pipeline failures.
The workaround is to unarchive affected repositories, roll out changes related to
github_repository_ruleset
and archive them again. Rather time-consuming process when handling hundreds of repositories.Debug Output
No response
Panic Output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: