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

version 1 of groups no longer work with schedule in resticprofile 0.29.0 #439

Open
stucki-stuck opened this issue Dec 2, 2024 · 2 comments

Comments

@stucki-stuck
Copy link

stucki-stuck commented Dec 2, 2024

Hello

This code worked in version 0.28.1. It doesn't work anymore in 0.29.0:

version: "1"

groups:
  all-backups:
    - nexus
...

the error in version 0.29.0 :

resticprofile --name all-backups schedule
2024/12/02 14:16:01 using configuration file: /etc/resticprofile/profiles.yaml
2024/12/02 14:16:01 no schedule found for profile 'all-backups'

this example is still in the doc :

# a group is a profile that will call all profiles one by one
groups:
  # when starting a backup on profile "full-backup",
  # it will run the "root" and "src" backup profiles
  full-backup:
    - root
    - src

It should be clarified whether this is a bug or a new feature in the way groups are written, in which case the documentation should be updated with the new procedure.

@creativeprojects
Copy link
Owner

Yes I see.

Previously it was loading the profile names of the group and scheduling the profiles independently : but actually this is kind of counter-intuitive because in v2 it's scheduling the group itself and not the profiles.

I could put the feature back but I think it could be a bit misleading?

schedule config v1 config v2
group profile schedules included in groups group schedules
profile profile schedules profile schedules

@stucki-stuck
Copy link
Author

Sorry for the late reply.

For me, the implementation doesn't matter as long as there is documentation to explain it.
I find it very useful to be able to schedule several projects in a single command.
I would like to keep this behavior even if the command or configuration must be changed.

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

2 participants