fix: correct cli-config 'import' parameters #3445
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.
Motivation
In an earlier piece of work, we converted the
import
command from rushstack to cmd-ts. In doing so, we mistakenly converted theoutput
parameter from an optional string, to a non-optional string.This causes the basemaps-config's Deploy Nonprod job to fail. The failing command and error are as follows:
Modifications
cli-config
package'simport
command'soutput
parameter to an optional string.cli
package'stsconfig.json
file to resolve type declaration errors.tsconfig.json
file's references for easier maintenance.Verification
I've captured a screenshot showing that the
import
command'soutput
parameter is now optional:I've also tested the
import
command locally with the--commit
flag omitted. The command does require a validconfig
, so I used a random one from the S3 bucket:We can see that the command executes successfully without requiring the
output
parameter: