-
Notifications
You must be signed in to change notification settings - Fork 932
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
[v8] Print max-in-flight value alongside deployment status #3097
Conversation
Co-authored-by: Greg Weresch <greg.weresch@broadcom.com>
…s table when it is set to non-default value (currently 1) Co-authored-by: Greg Weresch <greg.weresch@broadcom.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks clean and well written.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The change in general looks good.
Added some formatting nits(I think we should address these to try to get a consistently formated codebase) and some questions.
- these tests depend on a short-lived state
Co-authored-by: João Pereira <joaod@vmware.com>
ad7de47
to
483b5ee
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Description of the Change
This prints
max-in-flight: <value>
after the deployment status, when there is an Active deployment for an app and when max-in-flight is set to a non-default valueWith #3085 merged into
v8
, this PR takes the new changes from #3088 and targets thev8
branch.Why Is This PR Valuable?
It provides the user with information/confirmation that they have set a non-default max-in-flight value
+@joaopapereira @weresch @pivotalgeorge