CDK integration: Should infrastructure/*.out folders be committed to VCS?

aws / chalice

Python Serverless Microframework for AWS

Apache License 2.0

10.61k stars 1.01k forks source link

CDK integration: Should infrastructure/*.out folders be committed to VCS? #2098

Closed riverfr0zen closed 6 months ago

riverfr0zen commented 6 months ago

I'm following the Deploying with CDK tutorial, and not sure if the artifacts left in infrastructure/cdk.out and infrastructure/chalice.out should be committed to version control or not?

Right now they are not ignored by default, and they contain several tens of MBs of stuff. Is it okay to set a .gitignore rule to omit them from VCS, or will this be problematic when working with other devs?

brno32 commented 6 months ago

the .out folders should indeed be ignored. They are generated at build/deploy time and are not meant to be included in your VCS