fix: restore missing Gateway env without restart - #145
Merged
Merged
Conversation
Co-Authored-By: Codex <noreply@openai.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.
Gateway keepalive fails at environment loading when the deployment .env is missing; resetting the VM cannot restore it. Add a manual, single-target restore-env operation that reuses target-specific Secret Manager inputs, verifies the approved main SHA and compares the rendered configuration with the running container before creating only the missing file. Existing files and links are preserved; credentials are not logged. The operation skips source synchronization, secret updates, VM resets and container/watcher changes.
Validation: six offline remote-execution fixtures cover successful creation with matching content and mode 0600, existing files, symlinks, environment differences, port differences and bind-address differences. Repository required shell checks, actionlint and diff checks passed. Real restoration is a separate selected-target operation after merge.