Skip to content

Conversation

@gailwang
Copy link
Contributor

@gailwang gailwang commented Jul 2, 2020

The issue is:

$ terraform apply
2020/07/02 19:49:39 [WARN] Log levels other than TRACE are currently unreliable, and are supported only for backward compatibility.
  Use TF_LOG=TRACE to see Terraform's internal logs.
  ----
tencentcloud_mysql_instance.mysql_master: Refreshing state... [id=cdb-i5ire7nz]

An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
-/+ destroy and then create replacement

Terraform will perform the following actions:

  # tencentcloud_mysql_instance.mysql_master must be replaced
-/+ resource "tencentcloud_mysql_instance" "mysql_master" {
        auto_renew_flag   = 0
        availability_zone = "ap-guangzhou-3"
      + charge_type       = "POSTPAID" # forces replacement
        engine_version    = "5.7"
        first_slave_zone  = "ap-guangzhou-3"
      + force_delete      = false
      ~ gtid              = 1 -> (known after apply)
      ~ id                = "cdb-i5ire7nz" -> (known after apply)
        instance_name     = "testAccMysql"
      + internet_host     = (known after apply)
      ~ internet_port     = 0 -> (known after apply)
        internet_service  = 0
      ~ intranet_ip       = "10.66.199.250" -> (known after apply)
        intranet_port     = 3360
      ~ locked            = 0 -> (known after apply)
        mem_size          = 1000
      - parameters        = {} -> null
      - pay_type          = 1 -> null # forces replacement
        period            = 1
      + prepaid_period    = 1
        project_id        = 0
        root_password     = (sensitive value)
      - security_groups   = [] -> null
        slave_deploy_mode = 0
        slave_sync_mode   = 0
      ~ status            = 1 -> (known after apply)
      - tags              = {} -> null
      ~ task_status       = 0 -> (known after apply)
        volume_size       = 50
    }

Plan: 1 to add, 0 to change, 1 to destroy.

Do you want to perform these actions?
  Terraform will perform the actions described above.
  Only 'yes' will be accepted to approve.

  Enter a value:
Interrupt received.
Please wait for Terraform to exit or data loss may occur.
Gracefully shutting down...

Error: Error asking for approval: interrupted

after fix:

$ terraform apply
2020/07/02 19:50:50 [WARN] Log levels other than TRACE are currently unreliable, and are supported only for backward compatibility.
  Use TF_LOG=TRACE to see Terraform's internal logs.
  ----
tencentcloud_mysql_instance.mysql_master: Refreshing state... [id=cdb-i5ire7nz]

An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
  ~ update in-place

Terraform will perform the following actions:

  # tencentcloud_mysql_instance.mysql_master will be updated in-place
  ~ resource "tencentcloud_mysql_instance" "mysql_master" {
        auto_renew_flag   = 0
        availability_zone = "ap-guangzhou-3"
        engine_version    = "5.7"
        first_slave_zone  = "ap-guangzhou-3"
      + force_delete      = false
        gtid              = 1
        id                = "cdb-i5ire7nz"
        instance_name     = "testAccMysql"
        internet_port     = 0
        internet_service  = 0
        intranet_ip       = "10.66.199.250"
        intranet_port     = 3360
        locked            = 0
        mem_size          = 1000
        parameters        = {}
      - pay_type          = 1 -> null
        period            = 1
      + prepaid_period    = 1
        project_id        = 0
        root_password     = (sensitive value)
        security_groups   = []
        slave_deploy_mode = 0
        slave_sync_mode   = 0
        status            = 1
        tags              = {}
        task_status       = 0
        volume_size       = 50
    }

Plan: 0 to add, 1 to change, 0 to destroy.

@ghost ghost added size/M and removed size/XS labels Jul 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants