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

Terraform Destroy on Role Grant will remove ALL users in Role, not a specific user #189

Closed
knighteagle789 opened this issue May 7, 2020 · 5 comments
Labels
bug Used to mark issues with provider's incorrect behavior

Comments

@knighteagle789
Copy link

When I run a terraform Role_Grant, it adds the specific user as expected. But when I run the destroy afterward, it queries out and grabs All of the users for that role and removes them.

I would expect to only see the specific user that was added to the role to be removed from the role.

@ryanking ryanking added the bug Used to mark issues with provider's incorrect behavior label May 12, 2020
@ahaffar
Copy link

ahaffar commented Sep 22, 2020

i am having the same issue
version 0.15.0

@ryanking
Copy link
Contributor

@knighteagle789 did the plan list all users, or only the one in your configuration?

@ryanking
Copy link
Contributor

I think this may unfortunately end up being a result of the way we have to implement the read path for these resources. The grant resources all have to be exclusive currently.

@cstkpk
Copy link
Contributor

cstkpk commented Mar 31, 2021

@ryanking has there been any further discussion on this? I'm finding that if I've used the role_grants resource to grant a user to a role and then remove that user, the user will be destroyed but the entire role_grants object will also be destroyed, rather than just removing that user from the role_grants object.

When destroying a user or role, is it possible to remove only the users or roles granted in that particular module instead of destroying the role grant entirely?

@sfc-gh-asawicki
Copy link
Collaborator

We are closing this issue as part of a cleanup described in announcement. If you believe that the issue is still valid in v0.89.0, please open a new ticket.

@sfc-gh-asawicki sfc-gh-asawicki closed this as not planned Won't fix, can't repro, duplicate, stale Apr 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Used to mark issues with provider's incorrect behavior
Projects
None yet
Development

No branches or pull requests

5 participants