Skip to content

chore(infra): bump prod.tag to extended image (re-apply PR #323)#330

Merged
prez2307 merged 1 commit into
mainfrom
chore/bump-prod-tag-extended-v2
Apr 21, 2026
Merged

chore(infra): bump prod.tag to extended image (re-apply PR #323)#330
prez2307 merged 1 commit into
mainfrom
chore/bump-prod-tag-extended-v2

Conversation

@prez2307
Copy link
Copy Markdown
Contributor

Summary

Re-applies PR #323's prod.tag bump now that PR #329 decoupled the task-def ARN from a cross-stack Fn::ImportValue via SSM. container-stack can freely register a new task-def revision with the extended OpenClaw image — the SSM param value tracks the new ARN automatically, and no consumer imports the revision-embedded export.

Expected deploy behavior

  • isol8-prod-container: task-def resource updates → new revision (e.g. :22) → SSM param value updates → clean, no lock.
  • isol8-prod-service: no diff (still reads SSM). Backend tasks keep running on the OLD SSM value until restarted; --force-new-deployment on the backend service picks up the new ARN.

Follow-ups (post-deploy)

  • Force a backend restart so new provisions see the new SSM value.
  • Fleet rollout for existing containers via POST /container/updates with owner_id:"all".

🤖 Generated with Claude Code

Re-applies PR #323 now that PR #329 decoupled the task-def ARN from a
cross-stack Fn::ImportValue via SSM. container-stack can freely register
a new task-def revision with the extended OpenClaw image — the SSM param
value tracks the new ARN automatically, and no consumer imports the
revision-embedded export anymore.

After deploy:
- New provisions land on the extended image (clawhub baked in).
- Existing per-user services still launch from the task-def revisions
  they were registered against at provision time. Roll them forward via
  POST /container/updates with owner_id:"all" (banner + Update Now), or
  force-apply per-owner in a follow-up.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@prez2307 prez2307 merged commit a4e93e4 into main Apr 21, 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