borgmatic-collective/borgmatic
borgmatic-collective
/
borgmatic
15
57
Fork 40
Code Issues 54 Pull Requests 1 Actions Packages Releases 121 Activity

WIP: Add locking of borgmatic config file #254

Closed
drewkett wants to merge 9 commits from (deleted):configlock into main
pull from: (deleted):configlock
merge into: borgmatic-collective:main
Conversation 5 Commits 9 Files Changed 2 +6 -1
2 changed files with 6 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files
Showing only changes of commit 8d24b0a586 - Show all commits

3
borgmatic/commands/borgmatic.py
View File

@ -3,6 +3,7 @@ import json
import logging
import os
import sys
import fcntl
witten commented 2019-12-09 18:01:26 +00:00
Outdated
Review
Copy Link

tox -e isort will order imports for you.

`tox -e isort` will order imports for you.
from subprocess import CalledProcessError
import colorama
@ -575,7 +576,7 @@ def main(): # pragma: no cover
fcntl.flock(f.fileno(), fcntl.LOCK_EX | fcntl.LOCK_NB)
except IOError:
logger.critical("Failed to acquire lock for {}".format(config_filename))
sys.exit(0))
sys.exit(0)
locks.append(f)
summary_logs = parse_logs + list(collect_configuration_run_summary_logs(configs, arguments))

4
borgmatic/config/schema.yaml
View File

@ -32,6 +32,10 @@ map:
type: bool
desc: Stay in same file system (do not cross mount points). Defaults to false.
example: true
lock_config:
type: bool
desc: Lock config when running borgmatic to prevent multiple instances from running simultaneously
witten commented 2019-12-09 18:04:46 +00:00
Outdated
Review
Copy Link

You could add: ". Defaults to false." here. See other descriptions for an example.

You could add: ". Defaults to false." here. See other descriptions for an example.
example: true
witten commented 2019-12-03 01:01:31 +00:00
Review
Copy Link

The fact that it's locking the configuration file might just be an implementation detail as far as the user is concerned. What about calling this something like lock_client, lock_borgmatic, etc? I don't feel strongly about this in any case.

The fact that it's locking the configuration file might just be an implementation detail as far as the user is concerned. What about calling this something like `lock_client`, `lock_borgmatic`, etc? I don't feel strongly about this in any case.
drewkett commented 2019-12-03 06:52:39 +00:00
Review
Copy Link

Those sound better. I’ll fix it when I get the chance

Those sound better. I’ll fix it when I get the chance
drewkett commented 2019-12-03 19:28:14 +00:00
Review
Copy Link

I renamed it to lock_client and left it as a bool for now. I didn't see immediately the best way to do it with the config (and validation), but if you want to keep options open switching this to something like lock: "config" so that then you could add a lock: "everything option later would be an option.

I renamed it to `lock_client` and left it as a bool for now. I didn't see immediately the best way to do it with the config (and validation), but if you want to keep options open switching this to something like `lock: "config"` so that then you could add a `lock: "everything` option later would be an option.
drewkett commented 2019-12-03 19:29:27 +00:00
Review
Copy Link

I also wasn't sure if the example line is supposed to be the default value or not.

I also wasn't sure if the example line is supposed to be the default value or not.
witten commented 2019-12-03 21:19:54 +00:00
Review
Copy Link

A bool is fine for now, as far as I'm concerned.

example: is not usually the default value. In fact it's often the opposite of the default value in that it's demonstrating how you would override the default if you are so inclined. So example: true sounds right to me here, given that I'm assuming the default is false (don't lock).

A bool is fine for now, as far as I'm concerned. `example:` is not usually the default value. In fact it's often the *opposite* of the default value in that it's demonstrating how you would override the default if you are so inclined. So `example: true` sounds right to me here, given that I'm assuming the default is `false` (don't lock).
numeric_owner:
type: bool
desc: Only store/extract numeric user and group identifiers. Defaults to false.