Skip to content
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

[BUG]: Using a team ID for github_repository_collaborators causes churn #2414

Closed
1 task done
stevehipwell opened this issue Oct 7, 2024 · 3 comments · Fixed by #2420
Closed
1 task done

[BUG]: Using a team ID for github_repository_collaborators causes churn #2414

stevehipwell opened this issue Oct 7, 2024 · 3 comments · Fixed by #2420
Labels
Status: Up for grabs Issues that are ready to be worked on by anyone Type: Bug Something isn't working as documented

Comments

@stevehipwell
Copy link
Contributor

Expected Behavior

Based on the documentation I'd expect to be able to set team_id to the team ID and have no churn.

Actual Behavior

It looks like the team slug is stored in the state which is causing churn on every run.

Terraform Version

Terraform v1.7.5
on windows_amd64

Affected Resource(s)

  • github_repository_collaborators

Terraform Configuration Files

No response

Steps to Reproduce

No response

Debug Output

No response

Panic Output

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@stevehipwell stevehipwell added Status: Triage This is being looked at and prioritized Type: Bug Something isn't working as documented labels Oct 7, 2024
@github-project-automation github-project-automation bot moved this to 🆕 Triage in 🧰 Octokit Active Oct 7, 2024
@kfcampbell kfcampbell added Status: Up for grabs Issues that are ready to be worked on by anyone and removed Status: Triage This is being looked at and prioritized labels Oct 7, 2024
@kfcampbell kfcampbell moved this from 🆕 Triage to 🔥 Backlog in 🧰 Octokit Active Oct 7, 2024
@petergasper
Copy link

As a workaround, I was able to use the resource by replacing id with the slug
team {
permission = "pull"
team_id = data.github_team.repo_teams["xyz"].slug
}

@stevehipwell
Copy link
Contributor Author

@petergasper I saw this churn even when using the slug.

@petergasper
Copy link

@stevehipwell I did not, but I have changed it once I had the state file with resources in place. Maybe I got lucky with my setup. Should be fixed now 🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Up for grabs Issues that are ready to be worked on by anyone Type: Bug Something isn't working as documented
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants