[jeremya]

Copilot generates CloudFormation templates based on the Copilot-specific config files. There’s a place where you can add your own additional resources in CloudFormation syntax IIRC. It also has the ability to create a CodePipeline for app deployment. That creation is also done by generating a CloudFormation template and deploying it for the user. I’m not sure why it’s not clearly documented that this is happening, but it is a selling point to me because if I want to, I can “eject” from Copilot and just maintain/enhance the CloudFormation templates.

[Aeolun]

I have a hard time believing anyone would consider ejecting to CloudFormation a selling point.

[llarsson]

Could be nice to version control them. Some CLI stuff looks cool on a blog, but do you want to remember what commands you typed, and in what order, to bring up what production looked like two weeks ago manually?

[dkarl]

It's a cautious way to start working with a new tool. It's AWS, but there will still be bugs, especially for people with large or unusual deployments. You could use the tool to generate CloudFormation configs and then put them through a PR process. After six months of this with no bogus configs generated by the tool, you might decide you're on a well-paved road and make it part of your CI/CD pipeline.