-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
fix: correctly set the default value of StatusCheck
to nil
#7089
fix: correctly set the default value of StatusCheck
to nil
#7089
Conversation
a987f6a
to
91f3f9a
Compare
Codecov Report
@@ Coverage Diff @@
## main #7089 +/- ##
==========================================
- Coverage 70.48% 68.71% -1.78%
==========================================
Files 515 558 +43
Lines 23150 26116 +2966
==========================================
+ Hits 16317 17945 +1628
- Misses 5776 6947 +1171
- Partials 1057 1224 +167
Continue to review full report at Codecov.
|
91f3f9a
to
db285ca
Compare
hey @sbe-genomics , thanks for catching this and creating a fix! Would you mind rebasing this PR? the integration test failure is unrelated and we've merged a fix into main |
0b453fe
to
db285ca
Compare
@MarlonGamez done, thanks! |
Merging this change as the integration test failure is unrelated/needs to be fixed on our end |
FlagAddMethod: "Var", | ||
DefinedOn: []string{"dev", "debug", "deploy", "run", "apply"}, | ||
IsEnum: true, | ||
NoOptDefVal: "true", |
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.
This line needs to be reverted. It breaks specifying --status-check
without any arguments.
Description
The
statusCheck
option in thedeploy
config section was not working as expected. The value from the skaffold config was never picked up, however it was doing the right thing when--status-check
was used on the command line.This method was checking if the
StatusCheck
value was defined via the command line, and if so returning the value it was set to. However since the flag was set to incorrectly default to true, that method would always return true if--status-check=
was not set on the command line.This PR sets the default value of
StatusCheck
tonil
, as this lines up with its usage and typeBoolOrUndefined