-
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
Modify github_team_repository to accept slug as a valid team_id as well #693
Merged
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
07a53ab
First attempt
k24dizzle 4110c47
Add comment
k24dizzle bcafe1d
Attempt to modify unit tests
k24dizzle 3c21151
Edit docs to reflect change
k24dizzle 37e313b
Make sure team_id is set appropriately
k24dizzle 265d62d
fixing lint
k24dizzle 62e5fc1
add passing tests for `github_team_repository`
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems like the riskiest bit. What was your experience leading up to this diff?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In my testing, I didn't have this if statement at first.
I tried setting the
team_id
to be a team slug, and was able to plan and apply the following config to create a new team repo connection:When I tried another plan after that I expected that terraform would say that there would be no changes necessary. However, I got the following output:
When terraform refreshed the state, using this
resourceGithubTeamRepositoryRead
function, it would replace theteam_id
from a slug to the actual team id, making it think that it would need to replace this resource.So I added this if statement to avoid this situation. We want to make sure that the
team_id
field remains whatever the user set initially. The only situation I could think of where we would want to actually set thisteam_id
field here, would be when we were importing a team_repo resource, in which we would want to populate this field for the user.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Appreciate the detail here, thanks.