ci: prefer direct-key credentials for MPP e2e#14472
Merged
zerosnacks merged 8 commits intofoundry-rs:masterfrom Apr 28, 2026
Merged
ci: prefer direct-key credentials for MPP e2e#14472zerosnacks merged 8 commits intofoundry-rs:masterfrom
zerosnacks merged 8 commits intofoundry-rs:masterfrom
Conversation
brendanjryan
requested review from
0xrusowsky,
DaniPopes,
figtracer,
grandizzy,
mablr,
mattsse,
onbjerg,
stevencartavia and
zerosnacks
as code owners
Member
stevencartavia
approved these changes
Apr 28, 2026
mablr
approved these changes
Apr 28, 2026
zerosnacks
approved these changes
Apr 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
TEMPO_PRIVATE_KEYwithout requiringkeys.tomlCI MPP, while keepingTEMPO_KEYS_TOML_B64as a fallback during migrationWhy
The current MPP CI path depends on Tempo wallet keystore material and access-key provisioning. That is more fragile than a funded direct key because it can fail on expired access keys, missing keychain state, or chain-id mismatches in
key_authorization.Foundry already supports direct-key mode internally via
TEMPO_PRIVATE_KEY; this change lets the CI script and workflow use that path directly.