Best practices for Hooks? #600
-
|
Since both Plans and Repositories support Hooks, are there any recommended best practices, or pros/cons, for where to define hooks? I have 3 plans and 3 corresponding repositories: PlanA->RepoA, PlanB->RepoB, PlanC->RepoC. I have Hooks for Shoutrrr notifications on |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
This is a good question
If you're wanting notifications for system health events you should have those hooks configured at the repo level. The easiest way to move them might be to just stop backrest and manually edit the config, you can copy the json "hooks" section from your plans to your repos if you're comfortable editing the file -- the field name and properties are the same. |
Beta Was this translation helpful? Give feedback.
This is a good question
If you're wanting notifications for system health events you should have those hooks configured at the repo level.
The easiest way to move them might be to just stop backrest and manually edit the config, you can copy the json "hooks" section from your plans to your repos if you're comfortable editing the file -- the field name and properties are the same.