Terraform-provider-aws: resource_aws_codedeploy_deployment_group.go - Ec2TagSet option not available

[xriu]

Terraform Version

Terraform v0.11.1 - provider.aws v1.6.0

Affected Resource(s)

• aws_codedeploy_deployment_group

Terraform Configuration Files

resource "aws_codedeploy_deployment_group" "example" {
  app_name              = "${aws_codedeploy_app.example.name}"
  deployment_group_name = "example-group"
  service_role_arn      = "${aws_iam_role.example.arn}"

"ec2TagSet": { 
         "ec2TagSetList": [ 
            [ 
               { 
                  "Key": "KEY_AND_VALUE",
                  "Type": "Name",
                  "Value": "AppVersion-ABC"
               }
            ],
            [ 
               { 
                  "Key": "KEY_AND_VALUE",
                  "Type": "Region",
                  "Value": "North"
               }
            ],
         ]
      },
}

Expected Behavior

ec2_tag_set option to enable multiple tag support

Actual Behavior

ec2_tag_set option not defined in resource_aws_codedeploy_deployment_group.go but defined in codedeploy API ( https://github.com/terraform-providers/terraform-provider-aws/blob/master/aws/resource_aws_codedeploy_deployment_group.go )

References

Official documentation
https://docs.aws.amazon.com/codedeploy/latest/userguide/instances-tagging.html?icmpid=docs_acd_console

CodeDeploy API
https://github.com/terraform-providers/terraform-provider-aws/blob/master/vendor/github.com/aws/aws-sdk-go/service/codedeploy/api.go

Resource CodeDeploy
https://github.com/terraform-providers/terraform-provider-aws/blob/master/aws/resource_aws_codedeploy_deployment_group.go

[Haegin]

Looks like this is a dupe of #2073.

[bflad]

The ec2_tag_set argument has been added to the aws_codedeploy_deployment_group attribute via #4324 and will release with v1.17.0 of the AWS provider, likely in a week.

[hashibot[bot]]

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. Thanks!