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

Support for Key Vault EC-HSM Keys #1943

Closed
marty2bell opened this issue Sep 18, 2018 · 1 comment · Fixed by #1814
Closed

Support for Key Vault EC-HSM Keys #1943

marty2bell opened this issue Sep 18, 2018 · 1 comment · Fixed by #1814

Comments

@marty2bell
Copy link

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

Azure Key Vault supports EC-HSM keys that are not supported by the provider. In addition, it's not clear how you would define which curve to use (are these types in the provider). The examples and documentation focusses on RSA keys.

New or Affected Resource(s)

azurerm_key_vault_key

References

https://docs.microsoft.com/en-us/cli/azure/keyvault/key?view=azure-cli-latest#az-keyvault-key-create

  • #0000
@ghost
Copy link

ghost commented Jul 19, 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 Jul 19, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants