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

Provider produced invalid plan when addon_profile in ignore_changes #3428

Closed
kim0 opened this issue May 13, 2019 · 2 comments · Fixed by #4898
Closed

Provider produced invalid plan when addon_profile in ignore_changes #3428

kim0 opened this issue May 13, 2019 · 2 comments · Fixed by #4898

Comments

@kim0
Copy link

kim0 commented May 13, 2019

Terraform (and AzureRM Provider) Version

Terraform v0.12.0-rc1
+ provider.azuread v0.3.1
+ provider.azurerm v1.27.1
+ provider.helm v0.9.1
+ provider.kubernetes v1.6.2
+ provider.random v2.1.2

Affected Resource(s)

  • azurerm_kubernetes_cluster

Terraform Configuration Files

  lifecycle {
    ignore_changes = ["id", "service_principal", "addon_profile" ]
  }
...
}

Expected Behavior

It should at least ignore the k8s cluster

Actual Behavior


Provider "azurerm" has indicated "requires replacement" on
module.glazeregion.module.k8s.azurerm_kubernetes_cluster.k8s for a
non-existent attribute path cty.Path{cty.GetAttrStep{Name:"addon_profile"},
cty.IndexStep{Key:cty.NumberIntVal(0)},
cty.GetAttrStep{Name:"http_application_routing"},
cty.IndexStep{Key:cty.NumberIntVal(0)}, cty.GetAttrStep{Name:"enabled"}}.

Steps to Reproduce

I am trying to apply the workaround mentioned in #2993 (comment) till that issue is fixed. But in my case (TF 0.12rc), once I add "addon_profile" to ignore_changes, the provider produces an invalid plan!

@ghost
Copy link

ghost commented Nov 26, 2019

This has been released in version 1.37.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.37.0"
}
# ... other configuration ...

@ghost
Copy link

ghost commented Mar 29, 2020

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 29, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
3 participants