generated from terraform-ibm-modules/terraform-ibm-module-template
-
Notifications
You must be signed in to change notification settings - Fork 1
Closed
Labels
Description
Affected modules
Terraform CLI and Terraform provider versions
- Terraform version: terraform1.10
- Provider version:
2025/06/25 14:15:12 Terraform init | - Installing ibm-cloud/ibm v1.77.1...
2025/06/25 14:15:16 Terraform init | - Installed ibm-cloud/ibm v1.77.1 (self-signed, key ID AAD3B791C49CC253)
2025/06/25 14:15:17 Terraform init | - Installing hashicorp/time v0.13.0...
2025/06/25 14:15:20 Terraform init | - Installed hashicorp/time v0.13.0 (signed by HashiCorp)
2025/06/25 14:15:21 Terraform init | - Installing hashicorp/random v3.7.2...
2025/06/25 14:15:21 Terraform init | - Installed hashicorp/random v3.7.2 (signed by HashiCorp)
Terraform output
Debug output
Expected behavior
We had a previously deployed instance of Redis using IBM Cloud Projects.
We updated the disk size of the Redis instance in the config and selected Validate.
The disk size of the redis instance should be updated. None of the other resources managed by this config should be updated or replaced.
Actual behavior
You can see in the logs that the plan is to replace two secrets that were created as part of the Redis instance:
# module.secrets_manager_service_credentials[0].module.secrets["cm_redis_v72_jp_osa_prod_admin_pw"].ibm_sm_arbitrary_secret.arbitrary_secret[0] must be replaced
2025/06/25 14:16:01 Terraform plan | -/+ resource "ibm_sm_arbitrary_secret" "arbitrary_secret" {
# module.secrets_manager_service_credentials[0].module.secrets["gc--cm-redis-v72-jp-osa-dn-prod"].ibm_sm_service_credentials_secret.service_credentials_secret[0] must be replaced
2025/06/25 14:16:01 Terraform plan | -/+ resource "ibm_sm_service_credentials_secret" "service_credentials_secret" {
My assumption is that the ibm_sm_service_credentials_secret
wants to be replaced because it was rotated since the config was created:
Terraform detected the following changes made outside of Terraform since the
2025/06/25 14:16:01 Terraform plan | last "terraform apply" which may have affected this plan:
I'm not sure why it wants to replace the admin_pw
Steps to reproduce (including links and screen captures)
- Run
terraform apply
Anything else
By submitting this issue, you agree to follow our Code of Conduct