-
Notifications
You must be signed in to change notification settings - Fork 596
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[cfn-lint] E3030 for config resources #2228
Comments
(Recommended workaround with resource-level ignores) We're currently pulling that |
More details {
"op": "add",
"path": "/ValueTypes/AWS::Config::ConfigurationRecorder.ResourceTypes",
"value": {
"botocore": "config/2014-11-12/ResourceType"
}
}, https://github.com/boto/botocore/blob/develop/botocore/data/config/2014-11-12/service-2.json#L6481 Also doesn't seem to exist in the API docs too https://docs.aws.amazon.com/config/latest/APIReference/API_ResourceIdentifier.html This issue is also a reference boto/botocore#2535 |
cfn-lint version: (
cfn-lint --version
)cfn-lint 0.58.2
Description of issue.
Error on an invalid value for Compliance resourceTypes that is in fact valid
Please provide as much information as possible:
cfn-lint
and/or the latest Spec filesN/A using the latest version
When designing cfn template for scheduled rules, any value for ComplianceResourceTypes can be used as long as it is a valid AWS resource type (and not only a supported resource type).
When a scheduled rule is described in the template, cfn-lint should verify all AWS resources.
Suggestion :
Identifying an AWS scheduled rule is not easy as
MaximumExecutionFrequency
is not mandatory and cfn-lint evaluation could work this way:IF an invalid value for ComplianceResourceTypes AND MaximumFrequency is set AND ComplianceResourceType is a Valid AWS resource type, Then cfn-lint evaluation is positive
Cfn-lint uses the CloudFormation Resource Specifications as the base to do validation. These files are included as part of the application version. Please update to the latest version of
cfn-lint
or update the spec files manually (cfn-lint -u
)The text was updated successfully, but these errors were encountered: