Skip to content

Promote no-target deploy failure handling#13

Merged
OziinG merged 2 commits intomainfrom
dev
Apr 30, 2026
Merged

Promote no-target deploy failure handling#13
OziinG merged 2 commits intomainfrom
dev

Conversation

@OziinG
Copy link
Copy Markdown
Contributor

@OziinG OziinG commented Apr 30, 2026

Summary

  • Promotes SSM no-target fail-fast handling to main.
  • Deploy workflow now reports the EC2/SSM/tag blocker directly instead of looping on NO_TARGETS.

Verification

  • bash -n scripts/dispatch-ec2-deploy-ssm.sh
  • git diff --check

Follow-up for #3.

OziinG and others added 2 commits April 30, 2026 15:17
Make the EC2 deploy workflow stop with a clear target-registration error instead of looping on NO_TARGETS when no SSM-managed instance matches the configured tag.

Constraint: Manual deploy with GitHubActionsRole authenticated but found zero SSM target invocations for tag:Service=tomotono-route-console in ca-central-1.

Rejected: Waiting through the full polling loop | it hides the actionable EC2/SSM/tag blocker.

Confidence: high

Scope-risk: narrow

Directive: Keep no-target failures explicit; fix EC2 SSM management/tagging before rerunning deploy.

Tested: bash -n scripts/dispatch-ec2-deploy-ssm.sh; git diff --check.

Not-tested: Successful live deploy because no SSM target currently matches the configured selector.

Related: #3

Co-authored-by: OmX <omx@oh-my-codex.dev>
Merge PR #12 to fail fast when no SSM target matches.
@OziinG OziinG merged commit d21050d into main Apr 30, 2026
2 checks passed
@OziinG OziinG mentioned this pull request Apr 30, 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