Enable multi-app deploy support in webiny deploy command

[Copilot]

Overview

The webiny deploy command now supports deploying multiple apps in a single command invocation, enabling developers to deploy specific app combinations without having to run separate commands or deploy all apps.

What Changed

Before

The deploy command only supported two modes:

• Deploy a single app: yarn webiny deploy core --env dev
• Deploy all apps: yarn webiny deploy --env dev

After

You can now deploy multiple apps in one command:

# Deploy specific apps together
yarn webiny deploy core api --env dev

# Still works - single app
yarn webiny deploy core --env dev

# Still works - all apps
yarn webiny deploy --env dev

Implementation Details

1. Array Parameter Support

Added an explicit array: true property to the command parameter definition to support multiple app names. Updated GetCliRunnerService to properly handle array parameters by:

• Added array?: boolean property to ICommandParamDefinition interface
• Reading the array property from parameter definitions
• Automatically configuring them as arrays when registering with yargs
• Constructing command strings with .. suffix for array parameters (e.g., [apps..])

2. Handler Logic

The command handler checks if apps are specified and deploys them sequentially:

if (params.apps && params.apps.length > 0) {
    for (const app of params.apps) {
        await this.deployApp({ ...params, app });
    }
} else {
    // Deploy all apps (existing behavior)
}

3. Simplified Type Design

Uses a single, clean interface for deploy parameters:

• IDeployCommandParams - Single interface with optional apps?: AppName[] parameter
• IDeploySingleAppParams - Internal method deploys single app

The apps parameter is always an optional array. When undefined or empty, all apps are deployed. When specified with one or more values, only those apps are deployed.

Benefits

✅ Improved Developer Experience - Deploy exactly what you need without extra commands
✅ Fully Backward Compatible - All existing workflows continue to work
✅ Type Safe - Full TypeScript type checking maintained
✅ Clean API - Uses explicit array: true property and simplified interface design
✅ Simple & Intuitive - Single parameter interface with optional array, no discriminated unions

Files Changed

• packages/cli-core/src/abstractions/features/Command.ts - Added array property to parameter definition interface
• packages/cli-core/src/features/DeployCommand/DeployCommand.ts - Core command logic with simplified interface
• packages/cli-core/src/services/GetCliRunnerService/GetCliRunnerService.ts - Array parameter handling
• packages/cli-core/src/features/DeployCommand/deployOutputs/BaseDeployOutput.ts - Type consistency

Closes #[issue-number]

[!WARNING]

Original prompt

enable the webiny deploy command to also support yarn webiny core api --env dev

So in other words, from only being able to specify one app (like 'core'), this time we can specify multiple, like in this case 'core api'.

Check the DeployCommand.ts file, there the changes should happen.

LFG!

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[adrians5j]

@copilot

[adrians5j]

Do we want to use this weird syntax?

Can't we just make it array: true?

[Copilot]

Changed to use array: true property instead of the apps.. syntax. The parameter definition now explicitly declares array: true, which is cleaner and more intuitive. Commit: ada5145 → new commit

[adrians5j]

@copilot

[adrians5j]

I'd rather have a single app parameter, that is a single app or an array of apps. Or maybe even... Let's have it always be an array? Like apps: AppName[].

[Copilot]

Simplified to always use apps?: AppName[] as an optional array in a single IDeployCommandParams interface. Removed the separate IDeployNoAppParams and IDeployWithAppParams interfaces. Commit: 2568d72 → new commit