aws
[Feature] Idempotency
Today we use an automation process to create and deploy applications with copilot. But for each step, we need to check if resources already exist to avoid some failures.
So it would be fine if actions of copilot was idempotent (and copilot could be less 'terminal' oriented).
Example: copilot svc init fails if the service already exists. In my mind, copilot svc init should be reserved to create the manifest file (if needed), and copilot svc deploy should be the only command to create and deploy services.
Maybe in the version V2 ?
@rverpillot Thank you for your request. We will consider this request and notify you with the update when we have one.
Paper trail related to decision to change to current implementation: https://github.com/aws/copilot-cli/discussions/2899 https://github.com/aws/copilot-cli/issues/1381
