Skip to content

fix: replace version-environment-key on ECS deploys instead of appending - #7

Closed
roybrouwer wants to merge 1 commit into
mainfrom
fix/ecs-upsert-version-environment-key
Closed

fix: replace version-environment-key on ECS deploys instead of appending#7
roybrouwer wants to merge 1 commit into
mainfrom
fix/ecs-upsert-version-environment-key

Conversation

@roybrouwer

Copy link
Copy Markdown

Summary

  • ECS deploys with version-environment-key copied the running task definition and appended the env var on every deploy, so keys like DD_VERSION accumulated duplicate entries.
  • Upsert in place (and drop leftover duplicates) so each deploy writes a single current value, matching how Lambda already sets the key.

Test plan

  • go test ./engine/
  • Merge and cut a v* release so source-deployments (ploy @latest) picks this up before relying on version-environment-key: DD_VERSION for BFF.

Made with Cursor

Ploy copied the running task definition and appended the version env var
on every deploy, so DD_VERSION (and any other version-environment-key)
accumulated duplicate entries. Upsert in place and drop leftovers.

Co-authored-by: Cursor <cursoragent@cursor.com>
@roybrouwer

Copy link
Copy Markdown
Author

Closing per request — not pursuing this approach.

@roybrouwer roybrouwer closed this Aug 17, 2026
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.

1 participant