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
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.
If an issue is assigned to the 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 to hashibot, a community member has claimed the issue already.
Note: Objects have changed outside of Terraform
Terraform detected the following changes made outside of Terraform since the last "terraform apply":
# module.gke_c1.google_container_cluster.gke_master has been changed~ resource "google_container_cluster""gke_master" {
id = "projects/my-project-id/locations/europe-west1/clusters/tfl-prod-main"
name = "tfl-prod-main"# (29 unchanged attributes hidden)~ maintenance_policy {
+ maintenance_exclusion {
+ end_time = "2021-07-19T00:00:00Z"
+ exclusion_name = "part1"
+ start_time = "2021-07-03T00:00:00Z"
}
+ maintenance_exclusion {
+ end_time = "2021-08-12T00:00:00Z"
+ exclusion_name = "part2"
+ start_time = "2021-07-31T00:00:00Z"
}
+ maintenance_exclusion {
+ end_time = "2021-08-24T00:00:00Z"
+ exclusion_name = "part3"
+ start_time = "2021-08-12T01:00:00Z"
}
# (1 unchanged block hidden)
}
# (15 unchanged blocks hidden)
}
Unless you have made equivalent changes to your configuration, or ignored the relevant attributes using ignore_changes, the following plan may include actions to undo or respond to these changes.
─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
~ update in-place
Terraform will perform the following actions:
# module.gke_c1.google_container_cluster.gke_master will be updated in-place~ resource "google_container_cluster""gke_master" {
id = "projects/my-project-id/locations/europe-west1/clusters/tfl-prod-main"
name = "tfl-prod-main"# (29 unchanged attributes hidden)~ maintenance_policy {
- maintenance_exclusion {
- end_time = "2021-07-19T00:00:00Z" -> null
- exclusion_name = "part1" -> null
- start_time = "2021-07-03T00:00:00Z" -> null
}
- maintenance_exclusion {
- end_time = "2021-08-12T00:00:00Z" -> null
- exclusion_name = "part2" -> null
- start_time = "2021-07-31T00:00:00Z" -> null
}
- maintenance_exclusion {
- end_time = "2021-08-24T00:00:00Z" -> null
- exclusion_name = "part3" -> null
- start_time = "2021-08-12T01:00:00Z" -> null
}
# (1 unchanged block hidden)
}
# (15 unchanged blocks hidden)
}
Plan: 0 to add, 1 to change, 0 to destroy.
Expected Behavior
When removing maintenance exclusions windows from my configuration, they should also disappear from the GKE resource, and not still being visible in the console and constantly reappearing when i do a plan.
Actual Behavior
Maintenance exclusions are removed from the state, but not from the GKE cluster, so they still appear as external addition in the plan, and the plan wants to delete them again ...
Steps to Reproduce
1.1 Create a GKE cluster.
1.2 Add maintenance exclusions to this cluster using Terraform.
2.1 Remove these maintenance exclusions from your configuration.
2.2 Run terraform plan, it says it will be removing the maintenance exclusions.
2.3 Run terraform apply. Your maintenance exclusions are removed from the state, but not from the GKE cluster.
3.1 Run terraform plan again, Terraform detects the maintenance exclusions that still exists on the GKE cluster as external changes and wants to add them back ...
I guess the main difference with the issue referenced above is the usage of for_each in the maintenance_exclusion dynamic block.
Looking at the terraform-google-kubernetes-engine module i see they use the same logic for maintenance_exclusion.
The text was updated successfully, but these errors were encountered:
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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
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
Notes:
In my main configuration i call a module like this:
And here is the module:
And the plan:
Expected Behavior
When removing maintenance exclusions windows from my configuration, they should also disappear from the GKE resource, and not still being visible in the console and constantly reappearing when i do a plan.
Actual Behavior
Maintenance exclusions are removed from the state, but not from the GKE cluster, so they still appear as external addition in the plan, and the plan wants to delete them again ...
Steps to Reproduce
1.1 Create a GKE cluster.
1.2 Add maintenance exclusions to this cluster using Terraform.
2.1 Remove these maintenance exclusions from your configuration.
2.2 Run
terraform plan
, it says it will be removing the maintenance exclusions.2.3 Run
terraform apply
. Your maintenance exclusions are removed from the state, but not from the GKE cluster.3.1 Run
terraform plan
again, Terraform detects the maintenance exclusions that still exists on the GKE cluster as external changes and wants to add them back ...References
I guess the main difference with the issue referenced above is the usage of for_each in the maintenance_exclusion dynamic block.
Looking at the terraform-google-kubernetes-engine module i see they use the same logic for maintenance_exclusion.
The text was updated successfully, but these errors were encountered: