Open paulmossman opened 4 years ago
It's most likely because the scalable target has been recreated. There isn't currently a setting to control the deregistration delay on Shippable, but there are ways to avoid deleting and re-registering the scalable target. When the scalable target will be recreated depends on the deployment method. If it's blueGreen
, a new target won't be created unless minReplicas or maxReplicas is specified. For an upgrade
deployment method, the scalable target shouldn't be replaced unless the replicas settings have changed.
Description of your issue:
I'm deploying to an AWS Application Load Balancer. As per http://docs.shippable.com/platform/workflow/resource/loadbalancer/#oldSyntax , sourceName is the ARN of the target group. The deploys are successful.
From the AWS console I've change the target group's "Deregistration delay" from the default of 300s to a much smaller value.
The problem is that upon each Shippable deploy the "Deregistration delay" value is set back to 300s. Why is that? I cannot find Shippable configuration to control this.
Thank you.