Severity
1 report
Version
CLI version 2.20.1, Octopus Server Version 2026.2.9314
Latest Version
None
What happened?
When running the Octopus CLI command octopus deployment-target azure-web-app and supplying a custom worker pool via the --worker-pool argument, the worker pool value is ignored, and the default worker pool is set on the target instead.
Reproduction
- Create an Azure Web App
- Create/configure an Azure account in Octopus Deploy
- Configure the Octopus CLI
- Create an Azure web app deployment target via the CLI, while also supplying a custom worker pool via the
--worker-pool argument.
- Note that the target created in Octopus Deploy is using the default worker pool, despite passing a custom value for this.
Example command to run for step 4:
octopus deployment-target azure-web-app create --name azure-web-app/testing --worker-pool Test --environment Environments-1365 --role testservice --account Azure-Acct --web-app br-test --resource-group br-rg --tenanted-mode 'Untenanted'
Error and Stacktrace
More Information
No response
Workaround
No response
Severity
1 report
Version
CLI version 2.20.1, Octopus Server Version 2026.2.9314
Latest Version
None
What happened?
When running the Octopus CLI command
octopus deployment-target azure-web-appand supplying a custom worker pool via the--worker-poolargument, the worker pool value is ignored, and the default worker pool is set on the target instead.Reproduction
--worker-poolargument.Example command to run for step 4:
octopus deployment-target azure-web-app create --name azure-web-app/testing --worker-pool Test --environment Environments-1365 --role testservice --account Azure-Acct --web-app br-test --resource-group br-rg --tenanted-mode 'Untenanted'Error and Stacktrace
More Information
No response
Workaround
No response