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
resource"google_redis_instance""redis" {
depends_on=["google_compute_network.network"]
name="${var.env_name}-redis"display_name="${var.env_name}-redis: created by Terraform"tier="STANDARD_HA"memory_size_gb=1authorized_network="${google_compute_network.network.name}"# authorized_network = "${var.network_name}"region="${var.region}"location_id="europe-west1-b"alternative_location_id="europe-west1-c"redis_version="REDIS_3_2"
}
Debug Output
google_redis_instance.redis (new resource required)
id: "XXXXXXX/europe-west1/staging-redis" =><computed> (forces new resource)
alternative_location_id: "europe-west1-c" =>"europe-west1-c"
authorized_network: "projects/[PROJECT_NAME]/global/networks/staging" =>"staging" (forces new resource)
create_time: "2018-07-10T06:53:49.730848Z" =><computed>
current_location_id: "europe-west1-b" =><computed>
display_name: "staging-redis: created by Terraform" =>"staging-redis: created by Terraform"
host: "10.0.0.4" =><computed>
location_id: "europe-west1-b" =>"europe-west1-b"
memory_size_gb: "1" =>"1"
name: "staging-redis" =>"staging-redis"
port: "6379" =><computed>
project: "XXXXXXXXXX" =><computed>
redis_version: "REDIS_3_2" =>"REDIS_3_2"
region: "europe-west1" =>"europe-west1"
reserved_ip_range: "10.0.0.0/29" =><computed>
tier: "STANDARD_HA" =>"STANDARD_HA"
Expected Behavior
If redis resource configuration has not been changed, Terraform should not destroy the existing redis instance on GCP (Google Memorystore) and re-create it .
Actual Behavior
Terraform always destroys and re-createe redis instance on GCP.
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 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
Nov 17, 2018
Terraform Version
Terraform v0.11.7
Affected Resource(s)
Terraform Configuration Files
Debug Output
Expected Behavior
If redis resource configuration has not been changed, Terraform should not destroy the existing redis instance on GCP (Google Memorystore) and re-create it .
Actual Behavior
Terraform always destroys and re-createe redis instance on GCP.
The text was updated successfully, but these errors were encountered: