Skip to content
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

feat(servergroup): Allow users to opt-out of the target desired size check when verifying if the instances scaled up or down successfully (backport #4649) #4651

Merged
merged 2 commits into from
Mar 11, 2024

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Feb 22, 2024

This is an automatic backport of pull request #4649 done by Mergify.


Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

…check when verifying if the instances scaled up or down successfully (#4649)

* feat(servergroup): Allow users to opt-out of the target desired size check when verifying if the instances scaled up or down successfully

Some of our users prefer to use the actual instance size list to verify if everything was scaled up or down accordingly instead of relying on the target percentage. They noticed this is causing instability on their end

* chore: Update copyright

* refactor: Introduce the ServerGroupProperties which will be used to define all server group related properties

(cherry picked from commit f5fa468)
@spinnakerbot
Copy link
Contributor

Features cannot be merged into release branches. The following commits are not tagged as one of "fix, chore, docs, perf, test":

Read more about commit conventions and patch releases here.

@jasonmcintosh jasonmcintosh added the ready to merge Approved and ready for merge label Mar 11, 2024
@jasonmcintosh jasonmcintosh merged commit fd27f46 into release-1.33.x Mar 11, 2024
2 checks passed
@mergify mergify bot deleted the mergify/bp/release-1.33.x/pr-4649 branch March 11, 2024 21:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready to merge Approved and ready for merge target-release/1.33
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants