forked from cadence-workflow/cadence
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
The commands which used cluster names (domain register/update) were broken. Previously with urfave v1 we did a hack - we collected posional arguments and implicitely took all of them as clusters. Thus, these crazy invocations worked: ``` $ cadence domain register --clusters clusterA clusterB --other_opt ... $ cadence domain register --clusters clusterA --other_opt ... clusterB ... ``` urfave v2 requires posional arguments to be at the end (makes sense!), that's why the above invocations are not working. One could be very confused with error-message cadence-cli gives in this case. The solution is to make it explicit: ``` $ cadence domain register --clusters clusterA,clusterB $ cadence domain register --clusters clusterA --clusters clusterB # a bit weird IMO, I'd recommend the next example $ cadence domain register --cl clusterA --cl clusterB ``` I don't think we mention this anywhere in documentation, but I think the new approach is more obvious and, after all, it works! In anyway, the command' --help explains it nicely: "Clusters (example: --clusters clusterA,clusterB or --cl clusterA --cl clusterB)"
- Loading branch information
Showing
4 changed files
with
31 additions
and
23 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters