CLI: Fix support for -c
(--config
) shortcut
#10607
Merged
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.
Regression was accidentally introduced with #10332.
Back in v2, the resolution of
-c/--config
was hardcoded intolib/cli/resolve-input.js
. While in v3 it was generalized, and co-relies on schema, which defines this option only for service specific commands.Having that
-c
shortcut stopped being recognized on time, as initial CLI flags resolution (which precedes configuration file resolution), loads schema only for non-service command flagsThis patch ensures that before we attempt to resolve configuration filename, we have flags common for service specific commands also loaded from schema
Closes: #10601