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

[Update] Update config.yaml to Address Deprecated Options #276

Conversation

Psycho0verload
Copy link
Contributor

Description

While working on PR #275, I noticed that various options in the config.yaml are marked as deprecated and are slated for removal in future releases. The following warnings were issued:

/etc/borgmatic.d/config.yml: Configuration sections (like location:, storage:, retention:, consistency:, and hooks:) are deprecated and support will be removed from a future release. To prepare for this, move your options out of sections to the global scope.                                                                                                                                                             
/etc/borgmatic.d/config.yml: The checks option now expects a list of key/value pairs. Lists of strings for this option are deprecated and support will be removed from a future release.                                                                                                                                                                                                                                       
/etc/borgmatic.d/config.yml: The prefix option is deprecated and support will be removed from a future release. Use archive_name_format or match_archives instead. 

To address these, I've updated the config.yaml based on the official documentation here. The updated configuration works as expected, but without the deprecated warnings.

@grantbevis grantbevis merged commit 0aec3c9 into borgmatic-collective:master Oct 24, 2023
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

Successfully merging this pull request may close these issues.

None yet

2 participants