Validate default config.yaml with Yamllint #813
Labels
No Label
bug
data loss
design finalized
good first issue
new feature area
question / support
security
waiting for response
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: borgmatic-collective/borgmatic#813
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What I'm trying to do and why
I tried to validate config.yaml at Configuration reference using yamllint:
Steps to reproduce
No response
Actual behavior
No response
Expected behavior
Not necessary but its good if the config file passes yamllint
Other notes / implementation ideas
No response
borgmatic version
1.8.6
borgmatic installation method
pip
Borg version
borg 2.0.0b7
Python version
No response
Database version (if applicable)
No response
Operating system and version
Fedora 39
Thanks for submitting this. The "comment" isn't indented like its content because it's not a comment! The lines yamllint is complaining about are instead commented out example options. If you know of a better / more linty way to do this in YAML, I'd love to know about it.
And as for the warning about missing document start ("---"), my understanding is that it's optional.
And if you're looking to validate a borgmatic configuration file, I recommend:
borgmatic config validate --config yourfile.yaml
@witten I got this:
But when I tried to create repository without any encryption I get following warning:
Config File: LaptopGit.conf.yaml
I'm not sure how you're getting that error, as if you run
borgmatic rcreate
without the-e
/--encryption
flag, I'd instead expect an error like this:So, to help diagnose what's going on, can I see your full command output from borgmatic? Feel free to redact any output that's sensitive.
Also, side note that you shouldn't be using Borg 2.0 beta for any production systems. Stick with Borg 1.2 for that. (2.0 beta is fine for testing though.)
@witten Complete command:
Output:
Config file: https://0x0.st/HGbl.yaml
Issue: Contrary to error message the repository folder was created:
I believe that "does not exist" message is coming directly from Borg, but I'm not sure why. A few ideas to try:
I'm closing this one now due to inactivity, but I'd be happy to reopen or discuss further if you'd like! Thanks.