You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should be able to run terraform plan and apply on an existing cluster with the newest version of the provider without having to recreate the cluster entirely. We don't see this behavior on 1.33.1, although on that version the kube_admin_config is displayed instead of being marked sensitive.
Actual Behavior
terraform plan says it will destroy and recreate the AKS cluster as the server_app_secret will be computed.
Taking a look through this appears to be a duplicate of #4356 - rather than having multiple issues open tracking the same thing I'm going to close this issue in favour of that one; would you mind subscribing to #4356 for updates?
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
Mar 29, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Community Note
Terraform (and AzureRM Provider) Version
terraform:
v0.12.6
provider:
v1.34.0
Affected Resource(s)
azurerm_kubernetes_cluster
Terraform Configuration Files
Expected Behavior
We should be able to run
terraform plan
andapply
on an existing cluster with the newest version of the provider without having to recreate the cluster entirely. We don't see this behavior on1.33.1
, although on that version thekube_admin_config
is displayed instead of being marked sensitive.Actual Behavior
terraform plan
says it will destroy and recreate the AKS cluster as theserver_app_secret
will be computed.Steps to Reproduce
terraform plan
References
The text was updated successfully, but these errors were encountered: