Closed mgarber-ops closed 3 years ago
Looks like this is related to https://github.com/terraform-compliance/cli/issues/454
Hi @mgarber-ops,
Yours is a bit different as I understand. In your scenario, you filter out
resources with tags
with both on GIVEN
and WHEN
directives, but you don't drill down. Hence, the data Then it must contain <tags>
directive looks for everything, not only tags
A small change within your scenario would hit on the correct parameters ;
Scenario Outline: Ensure that specific tags are defined
Given I have resource that supports tags defined
Then it must have tags
And it must contain <tags>
And its value must match the "<value>" regex
....
Appreciate the speedy reply. I'll give this a shot later and let you know what happens
All is working now with your recommended changes. Thanks 👍🏻
Description
When deploying an ECS Task Definition with a container_definitions JSON that contains a list of maps for environment variables defined my tagging policy is incorrectly parsing them and treating them as a value for "tags"
To Reproduce
Feature File:
Plan File:
Sample Terraform Code:
Used
terraform-compliance
Parameters:Running via Docker:
YesError Output:
Expected Behavior: tags for resources should be in compliance with our .feature rule and pass with a zero exit code
Tested Versions:
v1.3.24
0.13.5
3
Additional Context: