Closed crerwin closed 1 month ago
Looking into this. Trying to figure out the extent of the issue. Docs point towards the upper case version but obviously the API is taking it case insensitive. There are cases where the value is case sensitive so trying to figure out that difference.
For this particular issue we may have to create a case insensitive enum check for the data we are getting from this source.
This seems to be specific to this resource type. So going to create a case insensitive json schema keyword to handle these use cases. Fix should be in shortly.
CloudFormation Lint Version
1.18.1
What operating system are you using?
Ubuntu
Describe the bug
This introduced a check on the value of batch compute environment that is too strict around case. We are linting CloudFormation generated by CDK so we don't have control over the case of the type enum.
I don't see that type enum specified in
aws-batch-computeenvironment.json
in the provider schemas. I'm not familiar with the cfn-lint code but I think this is an extra check added above and beyond the published schemas? Looks like either['managed', 'unmanaged', 'MANAGED', 'UNMANAGED']
needs to be supported or the check needs to be case-insensitive?Expected behavior
Linting should pass. This template has not changed, but its linting results changed with the updated version of
cfn-lint
.Reproduction template
It's tough to get an anonymized template as synthed by CDK, but this will give you the error in question (in addition to a few others because it's a partial template):