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
│ Error: PATCH https://api.github.com/repos/rtkwlf/test_repo: 422 Visibility can't be changed by this user. []
│
│ with github_repository.test_repo,
│ on repositories.tf line 31, in resource "github_repository" "test_repo":
│ 31: resource "github_repository" "test_repo" {
Expected Behavior
The repository should have been created with internal visibility
Actual Behavior
The repository was created with private visibility. Switching it to internal visibility failed.
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
terraform apply
Important Factoids
Our GitHub Organization only allows Administrators to change repository visibility and we want the terraform to be executable by non-administrator users
I'd like to see this corrected as well as our org only allows internal repository creation by its members. Creating a private repo and then switching its visibility will both be blocked with our currently configured settings.
Terraform Version
Provider Version
Affected Resource(s)
Please list the resources as a list, for example:
github_repository
Terraform Configuration Files
Debug Output
Expected Behavior
The repository should have been created with
internal
visibilityActual Behavior
The repository was created with
private
visibility. Switching it tointernal
visibility failed.Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
terraform apply
Important Factoids
Our GitHub Organization only allows Administrators to change repository visibility and we want the terraform to be executable by non-administrator users
References
internal
repositories in GHE organizations, but I suspect was only tested by an administrator or in an organization where non-administrator users can change repository visibilityThe text was updated successfully, but these errors were encountered: