Open eliskovets opened 2 months ago
Thanks for reporting this bug @eliskovets , at a first glance this appears to be the result of https://github.com/hashicorp/terraform-provider-aws/issues/19519
A fully-self contained example including a task that fails the health checks to reproduce this would be highly appreciated.
I guess it's more connected to the issue https://github.com/hashicorp/terraform-provider-aws/issues/20858
Describe what happened
When the ECS service has
deployment_circuit_breaker
configured withrollback=True
, even if deployment of a new version of task definition failed and ECS rolled back service to the previous stable version, pulumi still marks the deployment ofecs.Service
resources as successfullyupdated
.Sample program
Log output
No response
Affected Resource(s)
No response
Output of
pulumi about
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction. To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).