-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Requires replacement on google_container_cluster for non-existent attribute path #8038
Requires replacement on google_container_cluster for non-existent attribute path #8038
Comments
The workaround (I still think this is a bug, because it should not end up in this abysmal state) for anybody who is interested: private_cluster_config {
enable_private_endpoint = false
enable_private_nodes = false
# When enable_private_nodes is false, you can create a cluster with a master_ipv4_cidr_block.
# But any subsequent plan/apply on the cluster will fail with the error above.
# In theory you should not do that, but it might happen.
# So when enable_private_nodes is false, you must set master_ipv4_cidr_block to an empty string ""
master_ipv4_cidr_block = ""
} I am using the resource as part of a greater module, and therefore this combination of parameters popped up. For example: private_cluster_config {
enable_private_endpoint = false
enable_private_nodes = var.some_private_node_config
# When enable_private_nodes is false, you can create a cluster with a master_ipv4_cidr_block.
# But any subsequent plan/apply on the cluster will fail with the error above.
# In theory you should not do that, but it might happen.
# So when enable_private_nodes is false, you must set master_ipv4_cidr_block to an empty string ""
master_ipv4_cidr_block = var.some_private_node_config ? var.some_master_ipv4_cidr_block : ""
} |
@Overbryd here is what the document specifies about master_ipv4_cidr_block. |
@edwardmedia I think it should fail at an earlier stage rather 1) allowing to create the cluster with the wrong settings and 2) marking the cluster for replacement on a subsequent apply. |
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! |
Community Note
modular-magician
user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned tohashibot
, a community member has claimed the issue already.Terraform Version
Affected Resource(s)
Terraform Configuration Files
Debug Output
Expected Behavior
Actual Behavior
Steps to Reproduce
terraform apply
The text was updated successfully, but these errors were encountered: