feat(entrypoint): materialize aws-lambda class keys at container start#28
Merged
Conversation
Adds four materialize_key calls for the aws-lambda-{us-east-1,us-west-2,
eu-west-1,ap-northeast-1} substrates, alongside the existing
local-docker-v0 line.
After this lands and Fly redeploys, the hosted signer service produces
real class-signed identities for all five v3.0.0 substrates ready to
ship. The four AWS Lambda class keys were uploaded as Fly secrets and
are waiting for the entrypoint to materialize them on the next
container boot.
Modal and Akash entrypoint lines will be added when those substrate
adapters ship later in Phase 2.
Signed-off-by: VladimirEdouard <135543245+vje013@users.noreply.github.com>
Signed-off-by: VladimirEdouard <135543245+vje013@users.noreply.github.com>
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
1 participant
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.
Phase 2 step 3b-5. Adds four materialize_key lines for the aws-lambda-{region} substrates so the next Fly redeploy actually materializes the four secrets uploaded in step 3b-4. After this PR merges + Fly redeploys, /.well-known/substrate-keys.json publishes 5 keys instead of 1.