deploy: make the insforge-signup broker durable across redeploys#80
Merged
Conversation
setup-broker-tls.sh regenerated broker.conf with only `location /`, silently dropping any sidecar routes (e.g. the signup broker's /insforge/signup) on every redeploy. Now: - setup-broker-tls.sh injects verbatim location blocks from the broker-extra-locations instance-metadata key before `location /`. - startup.sh builds cmd/insforge-signup-broker and, when the insforge-signup-env metadata key is set, installs its env + systemd unit and (re)starts it — a no-op on VMs without that metadata. So a fresh deploy reproduces the sidecar broker + its nginx route from metadata instead of losing them.
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.
setup-broker-tls.shregeneratedbroker.confwith onlylocation /, so any sidecar route (the signup broker's/insforge/signup) was silently dropped on every redeploy.locationblocks from thebroker-extra-locationsinstance-metadata key, beforelocation /(literal — nginx vars are not bash-expanded).cmd/insforge-signup-brokerand, guarded on theinsforge-signup-envmetadata key, installs its env + systemd unit and (re)starts it. No-op on VMs without that metadata.A fresh deploy now reproduces the sidecar broker + its route from metadata instead of losing them. Verified on pilot-publish: regenerating
broker.confre-injects/insforge/signupand the signed endpoint keeps working.