COS LOG enable & kubernetes cluster attachment support node extra_agrs

[gailwang]

terraform apply
2020/12/22 11:42:28 [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.
  ----
data.tencentcloud_cam_policies.cosAccess: Refreshing state...

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

Terraform will perform the following actions:

  # tencentcloud_cam_role.cosLogGrant will be created
  + resource "tencentcloud_cam_role" "cosLogGrant" {
      + create_time = (known after apply)
      + description = "cos log enable grant"
      + document    = jsonencode(
            {
              + statement = [
                  + {
                      + action    = [
                          + "name/sts:AssumeRole",
                        ]
                      + effect    = "allow"
                      + principal = {
                          + service = [
                              + "cls.cloud.tencent.com",
                            ]
                        }
                    },
                ]
              + version   = "2.0"
            }
        )
      + id          = (known after apply)
      + name        = "CLS_QcsRole"
      + update_time = (known after apply)
    }

  # tencentcloud_cam_role_policy_attachment.cosLogGrant will be created
  + resource "tencentcloud_cam_role_policy_attachment" "cosLogGrant" {
      + create_mode = (known after apply)
      + create_time = (known after apply)
      + id          = (known after apply)
      + policy_id   = "1722911"
      + policy_name = (known after apply)
      + policy_type = (known after apply)
      + role_id     = (known after apply)
    }

  # tencentcloud_cos_bucket.mycos will be created
  + resource "tencentcloud_cos_bucket" "mycos" {
      + acl               = "private"
      + bucket            = "mycos-1259649581"
      + cos_bucket_url    = (known after apply)
      + id                = (known after apply)
      + log_enable        = false
      + versioning_enable = false
    }

  # tencentcloud_cos_bucket.mylog will be created
  + resource "tencentcloud_cos_bucket" "mylog" {
      + acl               = "private"
      + bucket            = "mylog-1259649581"
      + cos_bucket_url    = (known after apply)
      + id                = (known after apply)
      + log_enable        = false
      + versioning_enable = false
    }

Plan: 4 to add, 0 to change, 0 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: yes

tencentcloud_cam_role.cosLogGrant: Creating...
tencentcloud_cos_bucket.mycos: Creating...
tencentcloud_cos_bucket.mylog: Creating...
tencentcloud_cos_bucket.mycos: Creation complete after 4s [id=mycos-1259649581]
tencentcloud_cos_bucket.mylog: Creation complete after 4s [id=mylog-1259649581]
tencentcloud_cam_role.cosLogGrant: Still creating... [10s elapsed]
tencentcloud_cam_role.cosLogGrant: Creation complete after 11s [id=4611686018429277126]
tencentcloud_cam_role_policy_attachment.cosLogGrant: Creating...
tencentcloud_cam_role_policy_attachment.cosLogGrant: Still creating... [10s elapsed]
tencentcloud_cam_role_policy_attachment.cosLogGrant: Creation complete after 11s [id=4611686018429277126#1722911]

Apply complete! Resources: 4 added, 0 changed, 0 destroyed.

double apply

$ terraform apply
2020/12/22 11:43:00 [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.
  ----
data.tencentcloud_cam_policies.cosAccess: Refreshing state...
tencentcloud_cam_role.cosLogGrant: Refreshing state... [id=4611686018429277126]
tencentcloud_cos_bucket.mycos: Refreshing state... [id=mycos-1259649581]
tencentcloud_cos_bucket.mylog: Refreshing state... [id=mylog-1259649581]
tencentcloud_cam_role_policy_attachment.cosLogGrant: Refreshing state... [id=4611686018429277126#1722911]

Apply complete! Resources: 0 added, 0 changed, 0 destroyed.

change 1

terraform apply
2020/12/22 11:09: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_cam_role.cosLogGrant: Refreshing state... [id=4611686018429277126]
data.tencentcloud_cam_policies.cosAccess: Refreshing state...
tencentcloud_cos_bucket.mycos: Refreshing state... [id=mycos-1259649581]
tencentcloud_cos_bucket.mylog: Refreshing state... [id=mylog-1259649581]
tencentcloud_cam_role_policy_attachment.cosLogGrant: Refreshing state... [id=4611686018429277126#1722911]

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_cos_bucket.mycos will be updated in-place
  ~ resource "tencentcloud_cos_bucket" "mycos" {
        acl               = "private"
        bucket            = "mycos-1259649581"
        cos_bucket_url    = "mycos-1259649581.cos.ap-guangzhou.myqcloud.com"
        id                = "mycos-1259649581"
        log_enable        = true
      ~ log_prefix        = "cos-access-log/" -> "MyLogPrefix"
        log_target_bucket = "mylog-1259649581"
        versioning_enable = false
    }

Plan: 0 to add, 1 to change, 0 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: yes

tencentcloud_cos_bucket.mycos: Modifying... [id=mycos-1259649581]
tencentcloud_cos_bucket.mycos: Modifications complete after 3s [id=mycos-1259649581]

Apply complete! Resources: 0 added, 1 changed, 0 destroyed.

change 2

terraform apply
2020/12/22 11:26:27 [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_cam_role.cosLogGrant: Refreshing state... [id=4611686018429277126]
data.tencentcloud_cam_policies.cosAccess: Refreshing state...
tencentcloud_cos_bucket.mycos: Refreshing state... [id=mycos-1259649581]
tencentcloud_cos_bucket.mylog: Refreshing state... [id=mylog-1259649581]
tencentcloud_cam_role_policy_attachment.cosLogGrant: Refreshing state... [id=4611686018429277126#1722911]

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_cos_bucket.mycos will be updated in-place
  ~ resource "tencentcloud_cos_bucket" "mycos" {
        acl               = "private"
        bucket            = "mycos-1259649581"
        cos_bucket_url    = "mycos-1259649581.cos.ap-guangzhou.myqcloud.com"
        id                = "mycos-1259649581"
      ~ log_enable        = true -> false
      - log_prefix        = "MyLogPrefix" -> null
      - log_target_bucket = "mylog-1259649581" -> null
        versioning_enable = false
    }

Plan: 0 to add, 1 to change, 0 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: yes

tencentcloud_cos_bucket.mycos: Modifying... [id=mycos-1259649581]
tencentcloud_cos_bucket.mycos: Modifications complete after 4s [id=mycos-1259649581]

Apply complete! Resources: 0 added, 1 changed, 0 destroyed.

destroy

$ terraform destroy
2020/12/22 11:43:06 [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_cam_role.cosLogGrant: Refreshing state... [id=4611686018429277126]
data.tencentcloud_cam_policies.cosAccess: Refreshing state...
tencentcloud_cos_bucket.mycos: Refreshing state... [id=mycos-1259649581]
tencentcloud_cos_bucket.mylog: Refreshing state... [id=mylog-1259649581]
tencentcloud_cam_role_policy_attachment.cosLogGrant: Refreshing state... [id=4611686018429277126#1722911]

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

Terraform will perform the following actions:

  # tencentcloud_cam_role.cosLogGrant will be destroyed
  - resource "tencentcloud_cam_role" "cosLogGrant" {
      - console_login = false -> null
      - create_time   = "2020-12-22 11:42:32" -> null
      - description   = "cos log enable grant" -> null
      - document      = jsonencode(
            {
              - statement = [
                  - {
                      - action    = [
                          - "name/sts:AssumeRole",
                        ]
                      - effect    = "allow"
                      - principal = {
                          - service = [
                              - "cls.cloud.tencent.com",
                            ]
                        }
                    },
                ]
              - version   = "2.0"
            }
        ) -> null
      - id            = "4611686018429277126" -> null
      - name          = "CLS_QcsRole" -> null
      - update_time   = "2020-12-22 11:42:32" -> null
    }

  # tencentcloud_cam_role_policy_attachment.cosLogGrant will be destroyed
  - resource "tencentcloud_cam_role_policy_attachment" "cosLogGrant" {
      - create_mode = 2 -> null
      - create_time = "2020-12-22 11:42:43" -> null
      - id          = "4611686018429277126#1722911" -> null
      - policy_id   = "1722911" -> null
      - policy_name = "QcloudCOSAccessForCLSRole" -> null
      - policy_type = "QCS" -> null
      - role_id     = "4611686018429277126" -> null
    }

  # tencentcloud_cos_bucket.mycos will be destroyed
  - resource "tencentcloud_cos_bucket" "mycos" {
      - acl               = "private" -> null
      - bucket            = "mycos-1259649581" -> null
      - cos_bucket_url    = "mycos-1259649581.cos.ap-guangzhou.myqcloud.com" -> null
      - id                = "mycos-1259649581" -> null
      - log_enable        = false -> null
      - versioning_enable = false -> null
    }

  # tencentcloud_cos_bucket.mylog will be destroyed
  - resource "tencentcloud_cos_bucket" "mylog" {
      - acl               = "private" -> null
      - bucket            = "mylog-1259649581" -> null
      - cos_bucket_url    = "mylog-1259649581.cos.ap-guangzhou.myqcloud.com" -> null
      - id                = "mylog-1259649581" -> null
      - log_enable        = false -> null
      - versioning_enable = false -> null
    }

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

Do you really want to destroy all resources?
  Terraform will destroy all your managed infrastructure, as shown above.
  There is no undo. Only 'yes' will be accepted to confirm.

  Enter a value: yes

tencentcloud_cam_role_policy_attachment.cosLogGrant: Destroying... [id=4611686018429277126#1722911]
tencentcloud_cos_bucket.mycos: Destroying... [id=mycos-1259649581]
tencentcloud_cos_bucket.mylog: Destroying... [id=mylog-1259649581]
tencentcloud_cam_role_policy_attachment.cosLogGrant: Destruction complete after 0s
tencentcloud_cam_role.cosLogGrant: Destroying... [id=4611686018429277126]
tencentcloud_cam_role.cosLogGrant: Destruction complete after 1s
tencentcloud_cos_bucket.mycos: Destruction complete after 4s
tencentcloud_cos_bucket.mylog: Destruction complete after 4s

Destroy complete! Resources: 4 destroyed.

kubernetes cluster attachment set extra_args

terraform apply
2020/12/21 18:47:09 [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.
  ----
data.tencentcloud_vpc_subnets.vpc: Refreshing state...
data.tencentcloud_images.default: Refreshing state...
data.tencentcloud_instance_types.default: Refreshing state...
tencentcloud_kubernetes_cluster.managed_cluster: Refreshing state... [id=cls-dhzruogq]

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

Terraform will perform the following actions:

  # tencentcloud_instance.foo will be created
  + resource "tencentcloud_instance" "foo" {
      + allocate_public_ip                      = false
      + availability_zone                       = "ap-guangzhou-3"
      + create_time                             = (known after apply)
      + disable_monitor_service                 = false
      + disable_security_service                = false
      + expired_time                            = (known after apply)
      + force_delete                            = false
      + id                                      = (known after apply)
      + image_id                                = "img-25szkc8t"
      + instance_charge_type                    = "POSTPAID_BY_HOUR"
      + instance_charge_type_prepaid_renew_flag = (known after apply)
      + instance_name                           = "tf-auto-test-1-1"
      + instance_status                         = (known after apply)
      + instance_type                           = "S1.SMALL1"
      + internet_charge_type                    = (known after apply)
      + internet_max_bandwidth_out              = (known after apply)
      + key_name                                = (known after apply)
      + private_ip                              = (known after apply)
      + project_id                              = 0
      + public_ip                               = (known after apply)
      + running_flag                            = true
      + security_groups                         = (known after apply)
      + subnet_id                               = "subnet-1uwh63so"
      + system_disk_id                          = (known after apply)
      + system_disk_size                        = 50
      + system_disk_type                        = "CLOUD_PREMIUM"
      + vpc_id                                  = "vpc-h70b6b49"

      + data_disks {
          + data_disk_id          = (known after apply)
          + data_disk_size        = (known after apply)
          + data_disk_snapshot_id = (known after apply)
          + data_disk_type        = (known after apply)
          + delete_with_instance  = (known after apply)
          + encrypt               = (known after apply)
        }
    }

  # tencentcloud_kubernetes_cluster_attachment.test_attach will be created
  + resource "tencentcloud_kubernetes_cluster_attachment" "test_attach" {
      + cluster_id      = "cls-dhzruogq"
      + id              = (known after apply)
      + instance_id     = (known after apply)
      + labels          = {
          + "test1" = "test1"
          + "test2" = "test2"
        }
      + password        = (sensitive value)
      + security_groups = (known after apply)

      + worker_config {
          + docker_graph_path = "/var/lib/docker"
          + extra_args        = [
              + "root-dir=/var/lib/kubelet",
            ]
          + is_schedule       = true
        }
    }

Plan: 2 to add, 0 to change, 0 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: yes

tencentcloud_instance.foo: Creating...
tencentcloud_instance.foo: Still creating... [10s elapsed]
tencentcloud_instance.foo: Still creating... [20s elapsed]
tencentcloud_instance.foo: Creation complete after 20s [id=ins-pk0pbvk4]
tencentcloud_kubernetes_cluster_attachment.test_attach: Creating...
tencentcloud_kubernetes_cluster_attachment.test_attach: Still creating... [10s elapsed]
tencentcloud_kubernetes_cluster_attachment.test_attach: Still creating... [20s elapsed]
tencentcloud_kubernetes_cluster_attachment.test_attach: Still creating... [30s elapsed]
tencentcloud_kubernetes_cluster_attachment.test_attach: Still creating... [40s elapsed]
tencentcloud_kubernetes_cluster_attachment.test_attach: Still creating... [50s elapsed]
tencentcloud_kubernetes_cluster_attachment.test_attach: Still creating... [1m0s elapsed]
tencentcloud_kubernetes_cluster_attachment.test_attach: Still creating... [1m10s elapsed]
tencentcloud_kubernetes_cluster_attachment.test_attach: Still creating... [1m20s elapsed]
tencentcloud_kubernetes_cluster_attachment.test_attach: Still creating... [1m30s elapsed]
tencentcloud_kubernetes_cluster_attachment.test_attach: Still creating... [1m40s elapsed]
tencentcloud_kubernetes_cluster_attachment.test_attach: Still creating... [1m50s elapsed]
tencentcloud_kubernetes_cluster_attachment.test_attach: Still creating... [2m0s elapsed]
tencentcloud_kubernetes_cluster_attachment.test_attach: Still creating... [2m10s elapsed]
tencentcloud_kubernetes_cluster_attachment.test_attach: Creation complete after 2m20s [id=ins-pk0pbvk4_cls-dhzruogq]

Apply complete! Resources: 2 added, 0 changed, 0 destroyed.