-
Notifications
You must be signed in to change notification settings - Fork 766
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
github_repository_collaborator should accept both short-and-long-form repository name formats #256
Comments
I'd be happy to take care of this if it is approved for development. |
Hi @sudoforge. Thank you for opening this issue! We would be happy to accept a PR for this if you would like to open one. |
👋 Hey Friends, this issue has been automatically marked as |
well, this is a blast from the past. i can't add labels, but i'll try to make time for this over the next few weeks if it is still relevant. |
I've added the relevant labels. That sounds good to me, thank you! |
👋 Hey Friends, this issue has been automatically marked as |
Terraform Version
Affected Resource(s)
github_repository_collaborator
Terraform Configuration Files
Example configuration:
Debug Output
Irrelevant.
Panic Output
N/A
Expected Behavior
The
github_repository_collaborator
resource should have been created.Actual Behavior
A 404 error is received from the upstream API due to the endpoint not accepting the format of the name output by
github_repository.full_name
:PUT /repos/:owner/:repo/collaborators/:username
The GitHub API is inefficient and wildly inconsistent. This issue should be fixed upstream, but because it won't be, the Terraform provider should accept the
full_name
format and simply strip the:owner/
portion of the string, so that it is in parity with other resources, likegithub_repository_deploy_keys
, etc...Steps to Reproduce
some-username
to anythingterraform apply
Important Factoids
N/A
References
The text was updated successfully, but these errors were encountered: