Repository navigation
feature: update.sh can be run by the 5Stack service - #707
Merged
Merged
Conversation
- labels the node with the release version when there is no .git - stops instead of waiting when it would ask for a Steam key with no terminal - leaves Vault to the 5Stack service when it runs update.sh - lets the 5Stack service check each rendered overlay before it is applied
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
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.
Small, opt-in changes so the 5Stack service can run update.sh from a release bundle. Panels updating with ./update.sh behave exactly as before.
FIVESTACK_RELEASEwhen set, since a release bundle has no .gitapply_overlaycallsFIVESTACK_PRE_APPLYwith the rendered overlay before applying, and stops if it refuses (the service uses it to hold new matches when an apply would restart something without a zero-downtime rollout)apply_overlay_test.shplus three setup-env tests; each fails on main