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

Issues related to deleting role assignments within a locked Resource Group #225

Open
Salazander opened this issue Dec 11, 2024 · 0 comments

Comments

@Salazander
Copy link

Salazander commented Dec 11, 2024

I'm using an Azure Blob Storage Container as Terraform Backend.
The storage account is located within a resource group that is protected against deletion using a "cannot delete" lock.
Creating Dynamic Service Principals with the Storage Blob Data Contributor role works fine.
What does not work is the removal of the role assignment when the lease expires, since the role assignment "lives" within the locked resource group.

Questions:

  1. What is the general guidance on using dynamic service principals with roles scoped to resources within a locked resource group?
  2. I've noticed that the Vault (v1.15.4) relentlessly attempts to remove previous role assignments - Is there a way to prevent this behavior?
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

No branches or pull requests

1 participant