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

Managed HSMs are not purged #2348

Closed
heaths opened this issue Jun 3, 2023 · 1 comment · Fixed by #2349
Closed

Managed HSMs are not purged #2348

heaths opened this issue Jun 3, 2023 · 1 comment · Fixed by #2349
Labels
needs-triage For new issues

Comments

@heaths
Copy link
Member

heaths commented Jun 3, 2023

When running azd down --force --purge, Managed HSMs - a more secure, lifetime-billed Key Vault-like secure container - are not purged. These cost money even in deleted states and should be purged. Key Vaults, comparatively, are billed on a per-call basis so cost nothing when in a deleted state; though, if someone wants to reuse the same names, it can be a barrier.

@ghost ghost added the needs-triage For new issues label Jun 3, 2023
heaths added a commit to heaths/azure-dev that referenced this issue Jun 3, 2023
@heaths
Copy link
Member Author

heaths commented Jun 3, 2023

Found while working on heaths/azcrypto#36. Managed HSMs were not being purged nor was there any prompt. These are highly secure but expensive resources and are still billed in a deleted state.

@vhvb1989 vhvb1989 assigned vhvb1989 and unassigned vhvb1989 Jun 5, 2023
heaths added a commit that referenced this issue Jun 5, 2023
* Support purging of Managed HSMs

Fixes #2348

* Fix linting error
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-triage For new issues
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants