Skip to content

Use real vault + prod-latest tag when workflow_dispatch is run on main#27

Merged
rcurranmoz merged 1 commit into
mozilla-platform-ops:mainfrom
rcurranmoz:workflow-dispatch-prod-vault
May 14, 2026
Merged

Use real vault + prod-latest tag when workflow_dispatch is run on main#27
rcurranmoz merged 1 commit into
mozilla-platform-ops:mainfrom
rcurranmoz:workflow-dispatch-prod-vault

Conversation

@rcurranmoz
Copy link
Copy Markdown
Collaborator

Summary

PR #26 added workflow_dispatch as a trigger but didn't update the existing "push to main" conditionals in two places, so dispatched builds on main used the fake vault and pushed pr-{}-latest instead of prod-latest.

This PR extends both conditions to also accept workflow_dispatch on main:

  1. The bash check inside Determine vault & tags that sets ALIAS_TAG=prod-latest / BUILD_TAG=prod-${SHA}.
  2. The if: on Stage real vault into workspace that copies /etc/ronin/vault-real.yaml into the workspace.

Context

We hit this on the first workflow_dispatch attempt (run 25858509879) — the build ran with the fake vault and would have produced a non-prod tag even on success. The actual failure was a transient Apple IPSW download error at 57%, unrelated.

🤖 Generated with Claude Code

The previous PR added workflow_dispatch as a trigger but didn't update the
two existing 'push to main' gates. Result: dispatched builds on main used
the fake vault and produced a pr-{}-latest alias instead of prod-latest.

Extend both conditions (the determine-vault step's bash check and the
stage-real-vault step's if:) to also accept workflow_dispatch on main.
@rcurranmoz rcurranmoz merged commit dca7c82 into mozilla-platform-ops:main May 14, 2026
1 check failed
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