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

Inconsistent result bug with sentry_team_member resource #364

Closed
pgjones opened this issue Jan 2, 2024 · 7 comments · Fixed by #372
Closed

Inconsistent result bug with sentry_team_member resource #364

pgjones opened this issue Jan 2, 2024 · 7 comments · Fixed by #372

Comments

@pgjones
Copy link

pgjones commented Jan 2, 2024

As output by terraform apply,

Provider produced inconsistent result after apply
│ 
│ When applying changes to sentry_team_member.default["REDACTED"], provider "provider[\"registry.terraform.io/jianyuan/sentry\"]" produced an unexpected new value: .role: was
│ cty.StringVal("admin"), but now cty.StringVal("").
│ 
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.

I'm trying to add members to a team, happy to provide more information as requested.

@jianyuan
Copy link
Owner

jianyuan commented Jan 4, 2024

@pgjones Thanks for the report. Is the user already an organization-level admin or higher? I noticed that Sentry internally sets the role to null if the user already has better permissions and that causes an issue with Terraform.

@pgjones
Copy link
Author

pgjones commented Jan 4, 2024

One was, but I think this errors for all the users I've tried.

@jianyuan
Copy link
Owner

jianyuan commented Jan 8, 2024

@jianyuan
Copy link
Owner

I have devised a fix. I will be releasing v0.12.2 shortly.

@buzztaiki
Copy link

@jianyuan Thank you for fixing it! When do you think v0.12.2 will be released?

@jianyuan
Copy link
Owner

@buzztaiki It's out now!

@buzztaiki
Copy link

@jianyuan Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants