Fix CLI Does Not Honor metadata.namespace #1290
Closed
Conversation
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
dtaniwaki
reviewed
Apr 3, 2019
| @@ -102,6 +102,10 @@ func SubmitWorkflows(filePaths []string, submitOpts *util.SubmitOpts, cliOpts *c | |||
| } | |||
| } | |||
|
|
|||
| if !checkWfsInSameNs(workflows) { | |||
| log.Fatal("Workflows aren't at the same namespace") | |||
There was a problem hiding this comment.
Or should we rather create workflows of different namespaces one by one by loop?
There was a problem hiding this comment.
That's a good idea.
But for the below logic, like watch maybe will have some confuse. And check all the workflow are in the same ns. will help users to avoid mistakes on yaml file.
|
@sarabala1979 @jessesuen Any update ? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix #1288