To avoid confusion, I've updated the behavior of update command to fail if submission arguments are not provided with --submit.
Since there isn't good support from the parser library for handling option dependency (ref https://github.com/commandlineparser/commandline/issues/3), I had to handle this manually (i think it's okay since this is only applicable for update command and there could only ever be a handful of arguments that have dependency on --submit).
Now we can decide if we want this to be a "warning" behavior or a "blocking" behavior. I decided to go with a blocking behavior since users are likely to cancel the running update command or run submit command with --replace afterwards if they actually meant to use the replace behavior. Having it fail early makes user quickly recognize mistake and re-run the command with or without --replace.
Changes
Added support for
--replace
for submit command.To avoid confusion, I've updated the behavior of update command to fail if submission arguments are not provided with
--submit
.Since there isn't good support from the parser library for handling option dependency (ref https://github.com/commandlineparser/commandline/issues/3), I had to handle this manually (i think it's okay since this is only applicable for update command and there could only ever be a handful of arguments that have dependency on --submit). Now we can decide if we want this to be a "warning" behavior or a "blocking" behavior. I decided to go with a blocking behavior since users are likely to cancel the running update command or run submit command with --replace afterwards if they actually meant to use the replace behavior. Having it fail early makes user quickly recognize mistake and re-run the command with or without --replace.
Microsoft Reviewers: Open in CodeFlow