feat(templates): enable deployment circuit breaker for services

[efekarakus]

Resolves #1735

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[iamhopaul123]

LGTM! Do we need to update integ test for this change?

[efekarakus]

I checked and didn't seee anything that might break them, but I guess we'll see :D I'll monitor the pipeline

[mwarkentin]

@efekarakus We found there to be some issues with the way cloudformation interacts with the circuit breaker (aws/containers-roadmap#1205) outside of copilot. Does copilot deal with this better somehow?

[efekarakus]

Hey @mwarkentin ! Copilot v1.2.0 will display deployment progress while running copilot deploy, so you'll be able to tell that your service actually rolled back due to the circuit breaker kicking in:

Screen.Recording.2021-01-22.at.10.01.03.AM.mov

Unfortunately, the resource status will still be UPDATE_COMPLETE in CloudFormation. It's just that Copilot won't exit immediately unlike CFN and will keep monitoring the deployment rollout status until the rollout state is no longer in progress.

[mwarkentin]

@efekarakus thanks - so basically you highlight what's going on, but the user needs to take some action to get things back to working order (or in sync).

[efekarakus]

Yeah, unfortunately that's right

[mwarkentin]

No worries! 🤞 that the cloudformation integration improves at some point!