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
This issue is a design proposal for adding a flag to copilot [noun] deploy and copilot [noun] package that previews changes that will be made to the existing cloudformation stack. This will show what changes Copilot will make to existing and new resources, which will become especially useful when testing/deploying extensions via #4208 or #4209.
Proposal
A new flag, --diff, will be added to deploy and package commands that calculates and prints the diff between the deployed stack (including the addons stack!) and the stack that will be deployed or generated.
After displaying the diff, copilot [noun] deploy --diff will prompt with a confirmation like:
Continue with deployment? [y/N]:
before deploying the proposed changes.
copilot [noun] package --diff will print the diff and exit. The exit code will be as follows:
0 = no diffs found
1 = diffs found
2 = error producing diff
This should allow for a script to skip deploying a stack if no changes will occur.
UX Examples
Some examples of how a diff will look in different scenarios:
This issue is a design proposal for adding a flag to
copilot [noun] deploy
andcopilot [noun] package
that previews changes that will be made to the existing cloudformation stack. This will show what changes Copilot will make to existing and new resources, which will become especially useful when testing/deploying extensions via #4208 or #4209.Proposal
A new flag,
--diff
, will be added todeploy
andpackage
commands that calculates and prints the diff between the deployed stack (including the addons stack!) and the stack that will be deployed or generated.After displaying the diff,
copilot [noun] deploy --diff
will prompt with a confirmation like:before deploying the proposed changes.
copilot [noun] package --diff
will print the diff and exit. The exit code will be as follows:0 = no diffs found
1 = diffs found
2 = error producing diff
This should allow for a script to skip deploying a stack if no changes will occur.
UX Examples
Some examples of how a diff will look in different scenarios:
Adding a lambda function
Adding a statement to an IAM Role
AssumeRolePolicyDocument
:Updating an attribute of an IAM Role
AssumeRolePolicyDocument
:Changing the
ContainerPort
parameterThe text was updated successfully, but these errors were encountered: