Is this a feature or a bug?

• Feature
• Bug

Please describe the actual behavior.

When trying to do a rush deploy -s api I get the following

"ERROR: The deploy-api.json configuration specifies multiple items for
"deploymentProjectNames". Use the "--project" parameter to indicate the project
to be deployed.
"

Within the deploy-api.json I have multiple values under "deploymentProjectNames".

What is the expected behavior?

I want to implement this into a CI process without having to specify rush deploy commands for every project as they will continually grow and don't want developers having to change the CI scropts.

I'll be using a scaffold tool to scaffold the project and add the appropriate name into the deploy-api.json "deploymentProjectNames" array as well as rush.json.

I'd rather run rush deploy -s api once and for rush to handle creating the deployment folders for all projects defined against the "deploymentProjectNames" property.

I can then on the next step of my CI process point to the to common/deploy/* folders and action an deployment of each of the deployments that are created.