google_container_cluster does not import remove_default_node_pool correctly

[matti]

after importing a:

resource "google_container_cluster" "cluster" {
  ...
  remove_default_node_pool = true
}

I get this in plan:

  ~ google_container_cluster.cluster
      remove_default_node_pool: "" => "true"

which fails because the default-pool has already been removed

[matti]

added

  lifecycle {
    ignore_changes = "remove_default_node_pool"
  }

as a workaround

[emilymye]

Interesting - I'm not sure what the best thing to do is here for setting this value on import. Should we attempt to set it based on the presence of nodePools/default-pool? Thoughts @rileykarson?

[rileykarson]

That seems sensible to me, we could set it to false if GET succeeds and false otherwise; that way, the existing update logic we have that removes the default node pool when you go from false -> true will remove it on the next apply.

[ghost]

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!