Allow specify borg/borgmon version #107
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@m3nu Can you take a look a this ? |
|
Hi, sorry for the delay. Had this flagged, but didn't get to it yet. Looks fine. Good to merge after the tests are done. |
m3nu
approved these changes
Nov 22, 2022
|
Can you help to make the tests happy? Just replace |
|
Should be good now 👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This little PR is here to add the ability to specify the borg / borgmatic version to install.
This make the role able to upgrade / downgrade borg and borgmatic.
By default this role, will behave like before (Use last borg/borgmatic version on first install and don't upgrade on playbook re-run)