aws_launch_configuration Resource is Marked as Supporting Tags

[anthonycolon25]

I have an autoscaling group with and aws_launch_configuration. When I run the test it fails stating the following:

Scenario Outline: Ensure that specific tags are defined
        Given I have resource that supports tags defined
        When it contains tags
        Then it must contain <tags>

    Examples:
        | tags |
        | Name |
          Failure: aws_launch_configuration.example (resource that supports tags) does not have Name property.

When I add tags to the aws_launch_configuration resource in terraform and try to . build the plan it gives an error:

$ terraform plan -out=plan.out

Error: Unsupported argument

  on main.tf line 50, in resource "aws_launch_configuration" "example":
  50:   tags = [

An argument named "tags" is not expected here.

It doesn't look like aws_launch_configuration resources supports tags.

[eerkunt]

Is it possible to share plan.out.json for debugging, if it is not confidential ?

[anthonycolon25]

Here you go. One question that comes to mind is are aws_launch_configuration resources still valid in 0.12+? Should it be aws_launch_template?
plan.out.json.txt

[eerkunt]

Thanks! It looks like the problem is there due to resource mounting.

Will create a fix asap.

[anthonycolon25]

What is resource mounting?

[eerkunt]

This is a feature of terraform-compliance to comply with deeper tests created with terraform.

E.g. ;

resource "aws_security_group" "my_security_group" {
  name        = "some-sg"
  ...
}

resource "aws_security_group_rule" "my_security_rule_1" {
  type                     = "ingress"
  from_port                = 443
  to_port                  = 443
  protocol                 = "tcp"
  ...
  ...
  security_group_id        = "${aws_security_group.security_group.id}"
}

Where aws_security_group_rule.my_security_rule_1 is actually mounted on aws_security_group.my_security_group - which means, when terraform-compliance runs a test against aws_security_group.my_security_group, it should also check all the mounted resources against that resource.

Specifically, the bug in your scenario was, aws_autoscaling_group.example (which supports tags) was mounted over aws_launch_configuration.example and when we search for the tags within the values, it was returning True.

Now it is fixed with 1.0.8, please have a try :)

[anthonycolon25]

Tested with 1.0.8. it looks good. It is no longer failing for missing aws_launch_configuration tags.

Thanks.

[eerkunt]

Thanks for re-testing. Closing the issue.