feat(canopy): run hooks after a restore - #831
Merged
Merged
Conversation
Member
|
might as well support pre restore too? |
passcod
approved these changes
Aug 18, 2026
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
2 participants
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.
Stacked on #810. Paired restore lays a follower's data back down, but nothing can act on it afterwards:
pre/posthooks only run on backup.That is enough for postgres, whose method does its own stop/swap/start, and not enough for anything a service reads only at start. The case in hand is Tamanu's config key: it lives in podman's secret store, podman materialises a secret into a container when the container starts, so a restored store is inert until the units restart.
[[post_restore]]hooks, run after the def's own restore, fail-fast.