Conversation
This branch has not been deployed
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
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 PR adds a new
clickhouse_backuprole and playbook to create native ClickHouse database backups and upload them to remote storage using the existingstorage_backupsrole.The implementation is designed to work with Docker-based ClickHouse clusters while keeping native package installations supported as a secondary deployment mode. For Docker deployments, it writes the allowed backup disk configuration under
{{ CLICKHOUSE_BASE_DIR }}/config.d, stores backup artifacts in{{ CLICKHOUSE_DATA_DIR }}/backupson the host, and recreates the container throughdocker composewhen the backup disk configuration changes.The role discovers databases automatically or accepts an explicit list, creates one backup artifact per database, uploads the files to S3 or Azure, and cleans up temporary artifacts after upload.