[codex] Document build-time auth token setup#114
Merged
Conversation
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.
Summary
Documents the build-time secret prerequisite for policies that use
static_tokenauth gates.Why
The built-in base/admin examples reference
EDGE_ADMIN_TOKEN, and CloudFront Functions bake static token values into generated artifacts. Without that environment variable, the documented Quick Start build and doctor flow fails locally.Changes
EDGE_ADMIN_TOKENsetup before the Quick Start build command in English and Japanese READMEs.--allow-placeholder-tokenas a non-production fixture option.doctorshould run with the same environment variables asbuild.Validation
EDGE_ADMIN_TOKEN=ci-build-token-not-for-deploy npm run buildEDGE_ADMIN_TOKEN=ci-build-token-not-for-deploy node bin/cli.js doctor --no-report