azurerm_key_vault allow case-insensitive sku_name
#7290
Conversation
KeyVault API (2016-10-01) allows case-insensitive `Sku.name`, so we need to loose the constraint also in terraform, which should not be a breaking change.
|
@magodo - this sounds like a bug on the API/portal side for allowing the wrong casing to be used? and we should open an issue on the sdk/specs to bring attention to the service team? |
|
I'm going to close this for now as its been a month without a response - can reopen it once we're ready to move forward |
|
@katbyte I have submitted the issue and put the link in code. Do you think it is feasible to reopen this PR and label it as |
|
@magodo in this instance it sounds like the casing in the Swagger needs updating? |
|
@tombuildsstuff The API allows either case. Whilst I feel this PR should be safe to be merged as it just loosens some constraint. |
|
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 👉 [email protected]. Thanks! |
ghost
locked and limited conversation to collaborators
KeyVault API (2016-10-01) allows case-insensitive
Sku.name, so we needto loosen the constraint also in terraform, which should not be a
breaking change.
(fixes: #7254)