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

💡 Feature Request - Resource locks #43

Open
ReneHezser opened this issue Apr 15, 2024 · 2 comments
Open

💡 Feature Request - Resource locks #43

ReneHezser opened this issue Apr 15, 2024 · 2 comments
Labels
Area: Resource Guidance 📝 Improvements or additions to documentation Enhancement 🆕 New feature or request Type: Upstream Dependency ⬆️ something must happen before start something else

Comments

@ReneHezser
Copy link
Contributor

Describe the solution you'd like

Check for resource locks for every service that recommends it.

Describe alternatives you've considered

Some services are already checking for resource locks, but not all. e.g. NSG-3 - Configure locks for Network Security Groups to avoid accidental changes and/or deletion

Additional context

@ejhenry ejhenry added Area: Resource Guidance 📝 Improvements or additions to documentation Enhancement 🆕 New feature or request labels Apr 15, 2024
@tksh164
Copy link
Member

tksh164 commented Apr 18, 2024

I think that it is difficult to detect resource locks because Azure Resource Graph does not have the capability to achieve that currently. I believe that Azure Resource Graph does not have tables for Microsoft.Authorization/locks.

@ReneHezser
Copy link
Contributor Author

I think that it is difficult to detect resource locks because Azure Resource Graph does not have the capability to achieve that currently. I believe that Azure Resource Graph does not have tables for Microsoft.Authorization/locks.

Time to reenable PowerShell or az again ¯\(ツ)

The current situation with locks being checked only for very few services is not what I would expect. It brings inconsistency and causes questions why locks should only be applied on some resources.

@oZakari oZakari added the Type: Upstream Dependency ⬆️ something must happen before start something else label May 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Resource Guidance 📝 Improvements or additions to documentation Enhancement 🆕 New feature or request Type: Upstream Dependency ⬆️ something must happen before start something else
Projects
None yet
Development

No branches or pull requests

4 participants