-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Delay/Schedule automated AMI updates #328
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is this a BUG REPORT or FEATURE REQUEST?: Feature Request
Problem: When utilising #320 companies often have different tiers/channels of stability. Often they will want to have an AMI applied to development clusters, before being applied to production clusters.
Solution: Specify in configuration the amount of delay a cluster would like to add before updating the ASG configuration.
eg.
Would update the image ID 7 days after the SSM parameter is changed.
The text was updated successfully, but these errors were encountered: