Skip to content

Default Worker Pool not shown for deployment targets #600

@benPearce1

Description

@benPearce1

Severity

1 report

Originally reported in OctopusDeploy/Issues#10019

Version

Octopus CLI Version 2.21.1

Latest Version

None

What happened?

When running the Octopus CLI command deployment-target view against a Deployment Target that has an associated Worker Pool, the Worker Pool configuration details are not returned.

Reproduction

  1. Create an Azure web app Deployment Target in Octopus Deploy
  2. Associate a Worker Pool during the creation of the Deployment Target
  3. Run the deployment-target view Octopus CLI command against this Deployment Target, and note that the Worker Pool configuration is not returned.

Example Command:

octopus deployment-target view azure-web-app/testing -f json

Example Output:

{
  "Id": "Machines-7262",
  "Name": "azure-web-app/testing",
  "HealthStatus": "Healthy",
  "StatusSummary": "Octopus was able to successfully establish a connection with this machine on Wednesday, 13 May 2026 10:05:28 AM +00:00",
  "CommunicationStyle": "AzureWebApp",
  "Environments": [
    "Development"
  ],
  "Roles": [
    "testservice"
  ],
  "Tenants": null,
  "TenantTags": [],
  "EndpointDetails": {
    "Web App": "br-test"
  },
  "WebUrl": "https://example.octopus.app/app#/Spaces-522/infrastructure/machines/Machines-7262/settings"
}

Error and Stacktrace

More Information

No response

Workaround

Use the api command to do a GET request to the API directly

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions