You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running --stateful check on schema change, I have a situation where a property is going from accepting only type object to accepting type object or string. This seems like it should be considered backwards-compatible, but guard-rail is currently flagging it as a type change.
Repro steps:
Pull current IAM Role schema: aws cloudformation describe-type --type RESOURCE --type-name AWS::IAM::Role | jq -r .Schema > iam-role-schema.json
That is indeed not a breaking change according to CloudFormation definition of a backward compatibility. However, CDK team insisted on having this marked as a breaking change
Running
--stateful
check on schema change, I have a situation where a property is going from accepting only type object to accepting type object or string. This seems like it should be considered backwards-compatible, but guard-rail is currently flagging it as a type change.Repro steps:
aws cloudformation describe-type --type RESOURCE --type-name AWS::IAM::Role | jq -r .Schema > iam-role-schema.json
cp iam-role-schema.json iam-role-schema-modified.json
iam-role-schema-modified.json
soPolicyDocument
property has"type": "object"
.guard-rail --schema file:///path/to/iam-role-schema-modified.json --schema file:///path/to/iam-role-schema.json --stateful --format
Expected result
The text was updated successfully, but these errors were encountered: