hey @witten did you end up solving this? Sorry for the late response, my exam just ended.
Looks like
repository.get("label", repository["path"]) throughout the codebase is done to…
I discussed with witten that I'll implement the first option when I'm free from other GSoC tasks.
I was trying to back up all configs with:
location_config['source_directories'] = location_config.get('source_directories', []) + global_arguments.config_paths
Out of the…
Can you share your complete config? Looks like 'archive_name_format' is uncommented while it's parent key (storage) is commented.
One of the errors that says
At 'location.repositories[0]': {'path': '/srv/mergerfs/JGPool/BorgRepo', 'label': 'borgbase'} is not of type 'string'
is because of your Borgmatic…
Hi, I think this was fixed in 1.7.12 - borgmatic-collective/borgmatic#670
Hey, I started work on some other issues so I could not get a chance to look at this. I have my exams soon, so I'll be back to contributing actively after the first week of May.
If someone…
I think there are issues open for some of these too, could you link to them in the description so it's easier to close them? Anyway, I'll try to do that in some time.
No, I meant how borg config and borgmatic config would be separated.
Ugh, just remembered there's already a borg config that this would collide with. (Unless they could be made to coexist.)
generate-borgmatic-configcan becomeborgmatic config generate.validate-borgmatic-configcan becomeborgmatic config validate.
So did you make a design decision regarding…
I Was able to debug this:
The problem is with this line in info.py::display_archives_info() (line55):
flags.make_flags_from_arguments(
info_arguments, excludes=('rep…Glad it worked out!
I asked to see if there were a way to do it in borgmatic.
I don't think so.
I know that these are just format issues for the logging library and maybe similar to…
Nice, thanks for filing this!
For context, I recently worked on this PR - https://github.com/borgmatic-collective/borgmatic/pull/57, which allows users to tag/label a repo, hence changing the…
I can take this, it might make it easier for me to test monitoring hooks too.
Should I also add additional data gathered from the output of the create command to other monitoring hooks?
My bad, you can mark the PR as draft on gitea too btw.
@jetchirag does this PR add support for multiple actions only for cronitor? Every monitoring hook recieving the action_name and doing nothing with it seems a little off.
Maybe @witten can…
Maybe one of these tests (or an additional one) can have the ping_url instead of create as a key, now that we support it.
Also, if we are only using this variable when using_primary_action, it might make sense to rename it to primary_aciton_name and move it where it's needed too.
Not sure about this, but now that we don't have the required validation for anything, what will happen when I do this: