Remove logic for yaml history database format. #13
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
The yaml format is outdated. There is no point in continuing to support it. Where possible, old code is used to avoid unnecessary refactoring. Update tests.
Add build macOS to Linux. Update macOS to macOS. Nuances of using CGO with go-sqlite3.
Remove darwin from release.
woblerr
added
documentation
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.
The
yamlformat is outdated. There is no point in continuing to support it.Where possible, old code is used to avoid unnecessary refactoring.
If you are using an old
gpbackupversion that supports only the YAML formatgpbackup_history.yaml, then usegpbackup_exporter <= v0.3.0.The rpm and deb package build process has been updated. Now they are only being built for linux due to the need to use the flag
CGO_ENABLED=1.