-
Notifications
You must be signed in to change notification settings - Fork 151
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
Protection of core resources #4306
Comments
Terraform doesn't deal with removing resource locks particularly well from memory. |
Thanks for the suggestion, @West-P. I was thinking more of locks at the Azure level, with separate |
Feel free to add the locks if you are looking to prevent deletion via the portal. However as per @West-P 's comment Terraform just destroys the locks (ignores them). |
I see what you are saying, lock at the Azure level, not sure what Terraform would do in that case. @TonyWildish-BH have you tried this approach? Added a lock, and tried a |
No, haven't tried that. Was hoping to tap into the expertise here to see if someone had already tried anything. |
The issue I see is, in a production environment, typically manual commands are not run - its managed using IaC. Hence this "locking" this would need to be added to CI/CD, along with the removal and then it's of limited value and similar to the terraform implementation. |
We frequently deploy TREs for development alongside our production TRE, which comes with the risk that we may accidentally delete the production TRE if we're in the wrong terminal session when we type the deletion command. It would be great if the management and core resource groups could be locked against accidental deletion once they're deployed, with a flag in the config file to say if you want it locked or not.
I imagine that can be done without impeding the operation of the TRE. Any thoughts?
The text was updated successfully, but these errors were encountered: