Skip to content

Report AWS ECS target detail now the SDK deserialises the endpoint - #717

Merged
enf0rc3 merged 1 commit into
mainfrom
willlaugesen/fix-ecs-target-tests
Sep 1, 2026
Merged

Report AWS ECS target detail now the SDK deserialises the endpoint#717
enf0rc3 merged 1 commit into
mainfrom
willlaugesen/fix-ecs-target-tests

Conversation

@enf0rc3

@enf0rc3 enf0rc3 commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

Unit tests have been failing on main since the go-octopusdeploy bump to v2.116.0 in #708. That release added AwsEcsClusterEndpoint, so AWS ECS deployment targets no longer arrive with a nil endpoint, and five tests asserting the old unknown-type fallbacks started failing.

The target commands now name the type as "AWS ECS Cluster", show the cluster and region as endpoint details, and resolve the default worker pool. Tests that covered the nil-endpoint path now use a target with no endpoint at all, so the #604 regression stays guarded.

Verified with go test ./... from ./pkg: the three target packages that fail on main pass on this branch, and no other package changed state.

🤖 Generated with Claude Code

go-octopusdeploy v2.116.0 added AwsEcsClusterEndpoint, so ECS targets no
longer arrive with a nil endpoint. The target commands now name the type,
show the cluster and region, and resolve the default worker pool. The
tests that asserted the old unknown-type fallbacks cover a target with no
endpoint at all instead, keeping the #604 regression guarded.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@enf0rc3
enf0rc3 marked this pull request as ready for review September 1, 2026 02:59

@borland borland left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@enf0rc3
enf0rc3 merged commit b3c6c0f into main Sep 1, 2026
4 checks passed
@enf0rc3
enf0rc3 deleted the willlaugesen/fix-ecs-target-tests branch September 1, 2026 03:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants