Repository navigation
Keep reconciliation files private and release 0.9.3 - #14
Merged
Merged
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Keep uploaded WireGuard configurations in a private temporary directory and use owner-only temporary files for
wg syncconf. Remove temporary files after successful updates or rollback, while preserving updates without interface restarts. Prepare release 0.9.3.Validation:
bin/cipassed 64 tests with 202 assertions, RuboCop on 28 files, dependency audit and gem build. The regression tests execute the generated shell script under umask 022 and verify file permissions, cleanup and rollback. Both commits have verified signatures.