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

azurerm_key_vault problem is sku casing #4707

Closed
rdbartram opened this issue Oct 24, 2019 · 2 comments · Fixed by #4714
Closed

azurerm_key_vault problem is sku casing #4707

rdbartram opened this issue Oct 24, 2019 · 2 comments · Fixed by #4714
Milestone

Comments

@rdbartram
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

Terraform (and AzureRM Provider) Version

Terraform v0.12.12

  • provider.azuread v0.6.0
  • provider.azurerm v1.35.0
  • provider.random v2.2.1

Affected Resource(s)

azurerm_key_vault

Terraform Configuration Files

resource "azurerm_key_vault" "vh-core-infra" {
  name                        = "test"
  resource_group_name         = "test"
  location                    = "ukwest"
  enabled_for_disk_encryption = false
  tenant_id                   = "0000"

  sku_name = "standard"

}

Expected Behavior

After deployment the next plan should not say anything needs to be modified, when nothing actually has been modified

Actual Behavior

~ sku_name = "Standard" -> "standard"

Steps to Reproduce

  1. terraform plan

Important Factoids

I think this has only just started happening either today or in the last few days. Something in the ARM API must have changed

@ghost
Copy link

ghost commented Oct 29, 2019

This has been released in version 1.36.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example:

provider "azurerm" {
    version = "~> 1.36.0"
}
# ... other configuration ...

@ghost
Copy link

ghost commented Nov 24, 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 👉 [email protected]. Thanks!

@ghost ghost locked and limited conversation to collaborators Nov 24, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
2 participants