Repository navigation
Deploy public configuration as Worker variables - #133
Merged
Merged
Conversation
fengmk2
changed the title
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.
config/production.envcontains public settings, but deployments previously required a separate secret upload. This could leaveWORKSPACE_PACKAGESoutdated and reject new preview packages.Load these settings through
worker.varsinvoid.config.ts, so each deployment includes the current values. KeepADMIN_TOKENinenv.tsand remote secret storage. Production deployments continue to use OIDC without secret-write access.Existing projects must remove the old public entries from remote secret storage because those entries override
worker.vars. Secret deletion changes the running Worker immediately. The deployment guide describes the required migration during a maintenance window.