-
Notifications
You must be signed in to change notification settings - Fork 64
Add --wait switch on riff function create #689
Conversation
If this works out, we can do the same for other places where |
@@ -188,6 +189,13 @@ From then on you can use the sub-commands for the 'service' command to interact | |||
"verbose", "v", verboseUsage, | |||
).NoOptDefVal = "true" | |||
|
|||
command.Flags().VarPF( | |||
BroadcastBoolValue(false, |
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.
A broadcast value only makes sense if it is applied to several variables. This can be simplified to a more traditional cobra flag
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.
@ericbottard Fair enough, but I was copying the pattern employed elsewhere. I would prefer to raise an issue to apply the simplification throughout rather than "step out of line" in this PR.
cmd/commands/function.go
Outdated
@@ -137,6 +137,7 @@ From then on you can use the sub-commands for the 'service' command to interact | |||
} | |||
} else { | |||
printSuccessfulCompletion(cmd) | |||
fmt.Fprintf(cmd.OutOrStdout(), "Issue `riff service status %s` to see the status of the function\n", fnName) |
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.
Should this be printed only if not using --wait/--verbose
?
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.
@ericbottard Yes. Good catch. Fixed via force push.
Merged as 491d109 |
Fixes #682