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

warn destructive update only when count > 1 #13116

Closed
yaroot opened this issue May 25, 2022 · 2 comments
Closed

warn destructive update only when count > 1 #13116

yaroot opened this issue May 25, 2022 · 2 comments
Labels
stage/accepted Confirmed, and intend to work on. No timeline committment though. theme/bad-ux theme/cli type/enhancement

Comments

@yaroot
Copy link
Contributor

yaroot commented May 25, 2022

Proposal

Warn destructive update only when count > 1

Use-cases

Currently nomad cli warns destructive updates for all groups when MaxParallel > task_group.Count, even if the count is 1 or 0. It's more or less the intended behaviour: 1 is always destructive, 0 to deschedule the group.

Proposed Solutions

I can think of 2 solutions

@jrasell
Copy link
Member

jrasell commented May 26, 2022

Hi @yaroot that makes sense and thanks for raising a PR. We will get round to reviewing this soon.

@jrasell jrasell added theme/cli theme/bad-ux stage/accepted Confirmed, and intend to work on. No timeline committment though. labels May 26, 2022
@lgfa29
Copy link
Contributor

lgfa29 commented Feb 3, 2023

Fixed in #13103, so I'm going to close this one. Thank you once again for the fix @yaroot 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stage/accepted Confirmed, and intend to work on. No timeline committment though. theme/bad-ux theme/cli type/enhancement
Projects
Development

No branches or pull requests

3 participants