Open rittneje opened 1 year ago
Adding to the weirdness, even though CloudFormation spits out a validation error, the template is applied correctly anyway. It seems like the validation logic is case-sensitive but the apply logic isn't?
@rittneje , Can you pls check if you still see this issue?
@sethusrinivasan Yes this is still an issue
With this release we should see the failures going forward:
from template
Resources:
Bucket:
Type: AWS::S3::Bucket
Properties:
bucketName: !Sub "${AWS::StackName}-${AWS::Region}"
That being said I'm looking into why the template you provided doesn't provide the same error.
Name of the resource
AWS::Timestream::Table
Resource Name
No response
Issue Description
Note: This seems to apply to all CloudFormation resources. I just picked AWS::Timestream::Table because that is one I know is affected.
There is an existing bug in CDK that causes it to generate invalid templates. See https://github.com/aws/aws-cdk/issues/8996
However, the bigger issue is that CloudFormation does not actually reject the template. Instead, it only spits out a warning to the event log like so:
Expected Behavior
CloudFormation should fail if the template contains unrecognized properties.
Observed Behavior
It logs a warning but otherwise ignores the invalid properties.
Test Cases
Other Details
No response