fix(hosted): run the eSignet seeder once - #31
Merged
Conversation
Coolify gives a service that declares no restart policy `unless-stopped`, so the seeder exits 0 on success and is started again forever. Every other one-shot in the fleet already says `no`. Signed-off-by: Jeremi Joslin <jeremi@joslin.fr>
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.
esignet-seeddeclares no restart policy, so Coolify gives itunless-stopped.It exits 0 after seeding and is then started again forever: the deployed
container sits in
Restarting (0)and re-runs the idempotent seed on a loop.Every other one-shot in the fleet (
audit-permissions,mint-readiness, theTransit initializers, the provisioners) already declares
restart: "no".Found while deploying the authority-cells eSignet application. A topology test
now asserts the policy so it cannot be dropped again.