New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extending Copilot with CloudFormation YAML patches #4209
Labels
type/design
Issues that are design proposals.
Comments
Hi folks!! I'm really excited to say that AWS Copilot v1.27 is out and YAML patch extensions is now supported! 🚀
I'll close the issue now! If you have any questions, feedback, or suggestions please feel free to open new GitHub issues 🥳 |
This was referenced Apr 25, 2023
This was referenced Jul 5, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This issue is a design proposal that is an alternative to #4208. The goal is the same:
However, the user experience in this design document targets clients that need only tiny modifications and don't want to have the AWS Cloud Development Kit (CDK) as a dependency.
Proposal
Instead of using the CDK, we propose allowing clients to write CloudFormation YAML patches. The authoring experience should be familiar to customers that already use task definition overrides but expanded to all resources abstracted by the manifests.
copilot [noun] override
command, if the client opts into CloudFormation YAML patches then we will generate a single file as outputcfn.patches.yml
:add
,remove
,replace
operations.The authoring experience with
cfn.patches.yml
is optimized for tiny CloudFormation tweaks. It's not as flexible and safe as #4208, however it does not depend on any other tools and has a faster learning curve.Feedback
Please let us know your thoughts on the proposal above 🙇. Would this proposal unblock you?
The text was updated successfully, but these errors were encountered: