(aws-ec2): Empty content InitFile fails in CloudFormation #13009
Labels
@aws-cdk/aws-ec2
Related to Amazon Elastic Compute Cloud
bug
This issue is a bug.
effort/small
Small work item – less than a day of effort
good first issue
Related to contributions. See CONTRIBUTING.md
needs-triage
This issue or PR still needs to be triaged.
p2
This is not really a bug I would say but more of a missing validation, I tried to create a marker file with CfnInit:
But when cfn-init ran on the host I got:
It looks like this is not allowed in CloudFormation (not ideal but fine), so we should add some validation for the InitFile on the content (I realize this is might not possible for ALL types, e.g. S3, but still worth it for simple ones)
Reproduction Steps
Trying to add an empty InitFile using any way
What did you expect to happen?
Getting a failure during synth instead of waiting till I actually deploy.
What actually happened?
Environment
Other
This is 🐛 Bug Report
The text was updated successfully, but these errors were encountered: