Open nadove-ucsc opened 9 months ago
@nadove-ucsc The input for the filter_criteria based on your example should be ecr_image_repository_name
instead of repository_name
. You should be able to deploy it via the below configuration, if you were still having the issues.
resource "awscc_inspectorv2_filter" "name" {
filter_action = "SUPPRESS"
filter_criteria = {
ecr_image_repository_name=[{
comparison = "EQUALS"
value = "docker.io/cllunsford/aws-signing-proxy"
}]
}
name = "example-filter"
}
Community Note
Terraform CLI and Terraform AWS Cloud Control Provider Version
Terraform v1.3.10 on linux_amd64
providers.json
:Affected Resource(s)
Terraform Configuration Files
Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.
Debug Output
Panic Output
Expected Behavior
We expect a filter to be created, using the filter criteria as is documented. Note that
filter_criteria
(snake case) is documented as a required attributeActual Behavior
The deployment fails because the
filter_criteria
key is not recognized. Terraform claims that it should be spelled "FilterCriteria".Using
FilterCriteria
in the resource config instead offilter_criteria
results in a validation error that points back tofilter_criteria
being the correct spelling: