Allow Riff-Raff to update both Applications ASGs during GuCDK migration #27979
+2
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What is the value of this and can you measure success?
We are dual-stacking Applications as we migrate it to GuCDK. This means all infrastructure components (load balancer, autoscaling group, instances etc.) are temporarily duplicated.
Riff-Raff normally expects to find exactly one matching autoscaling group for a set of tags. When deploying it will update the application code for that autoscaling group only. If Riff-Raff finds more than one autoscaling group with the same set of tags the deployment will fail.
This change adds the
asgMigrationInProgress
to allow Riff-Raff to update both Applications autoscaling groups when deploying.This relies on https://github.com/guardian/platform/pull/1847 being applied first.
Checklist
Validated with Riff-Raff