-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Update Usage for Activation Poll #2398
Conversation
@mdeuser, please review. |
@@ -217,8 +217,8 @@ var activationResultCmd = &cobra.Command{ | |||
} | |||
|
|||
var activationPollCmd = &cobra.Command{ | |||
Use: "poll [NAMESPACE]", | |||
Short: wski18n.T("poll continuously for log messages from currently running actions"), | |||
Use: "poll [ NAMESPACE | ENTITY_NAME ]", |
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.
since the list is limited, i think the more explicit poll [NAMESPACE | ACTION_NAME | TRIGGER_NAME | RULE_NAME]
is helpful
new syntax LGTM |
@@ -217,8 +217,8 @@ var activationResultCmd = &cobra.Command{ | |||
} | |||
|
|||
var activationPollCmd = &cobra.Command{ | |||
Use: "poll [NAMESPACE]", | |||
Short: wski18n.T("poll continuously for log messages from currently running actions"), | |||
Use: "poll [ NAMESPACE | ACTION_NAME | TRIGGER_NAME | RULE_NAME ]", |
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.
👍
@bjustin-ibm, can you merge this one too? |
* Update Usage for Activation Poll
* Update Usage for Activation Poll
* Update Usage for Activation Poll
* Update Usage for Activation Poll
* Update Usage for Activation Poll
* Update Usage for Activation Poll
Make Activation Poll usage inform users that an entity name (action, trigger, or rule) can be provided as an optional argument.
Closes: #2273