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

Add enableSoftDelete and enablePurgeProtection attributes to Keyvault #2066

Closed
LaurentLesle opened this issue Oct 12, 2018 · 2 comments
Closed

Comments

@LaurentLesle
Copy link
Contributor

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

Add enableSoftDelete and enablePurgeProtection attributes to KeyVault
Required to support Storage Account Encryption with Keyvault
https://docs.microsoft.com/en-us/rest/api/keyvault/vaults/vaults_createorupdate

New or Affected Resource(s)

  • azurerm_keyvault

Potential Terraform Configuration

# Copy-paste your Terraform configurations here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file. For
# security, you can also encrypt the files using our GPG public key.

References

  • #0000
@tombuildsstuff
Copy link
Contributor

hi @LaurentLesle

Thanks for opening this issue :)

Support for soft-deleting Key Vaults has previously been requested in #1329 - rather than having multiple issues open tracking the same thing I'm going to close this issue in favour of that one - please subscribe to that issue for updates.

Thanks!

@ghost
Copy link

ghost commented Mar 6, 2019

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!

@ghost ghost locked and limited conversation to collaborators Mar 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants