Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[feature request] Condition section in profile #143

Open
tj57 opened this issue Sep 7, 2022 · 2 comments
Open

[feature request] Condition section in profile #143

tj57 opened this issue Sep 7, 2022 · 2 comments

Comments

@tj57
Copy link

tj57 commented Sep 7, 2022

What do you think about new condition section in the profile, and in it a list of conditions that must be met (logic AND) to proceed with each action, backup, prune etc. in this profile ?

You could call a script to check if the VPN tunnel or VM is working, etc.

profiles:
  photos:
     condition:
     - check_if_vpn_working.sh
     - check_if_vm_working.sh

It can be usefull in issue 135

@jkellerer
Copy link
Collaborator

Think we had discussed this for a possible remote shell / remote backup feature ( #69 ):
A conditional configuration that allows to have a single profiles.yaml running on different hosts where individual profiles decide whether they should be skipped or not depending on the conditions.

Might be a good addition even without remote shell (which probably takes time to arrive).

@uwe-schwarz
Copy link

I was just looking for something like this. I have a scheduled backup to a local (external) disk, but this disk is most of the time at home and so the backup fails every time I'm away from home and I get a notification (send-after-fail) for that.

I also would like to have conditions, I could also settle for a way to stop the backup without failing in a run-before. Maybe just something like: if the run-before exit-code is 127 don't trigger send-after-fail.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants