Release 2.1.0

[Slach]

v2.1.0

IMPROVEMENTS

• complex refactoring to use contexts, AWS and SFTP storage not full supported
• complex refactoring for logging to avoid race condition when change log level during config reload
• improve kubernetes example for adjust incremental backup, fix 523
• add storage independent retries policy, fix 397
• add clickhouse-backup-full docker image with integrated kopia, rsync, restic and clickhouse-local, fix 507
• implement GET /backup/kill?command=XXX API to allow kill, fix 516
• implement kill "full command" in POST /backup/actions handler, fix 516
• implement watch in POST /backup/actions handler API and CLI command, fix 430
• implement clickhouse-backup server --watch to allow server start watch after start, fix 430
• update metric last_{create|create_remote|upload}_finish metrics values during API server startup, fix 515
• implement clean_remote_broken command and POST /backup/clean/remote_broken API request, fix 520
• add metric number_backups_remote_broken to calculate broken remote backups, fix 530

BUG FIXES

• fix keep_backups_remote behavior for recursive incremental sequences, fix 525
• for restore command call DROP DATABASE IF EXISTS db SYNC when pass --schema and --drop together, fix 514
• close persistent connections for remote backup storage after command execution, fix 535
• lot of typos fixes

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	Secret	Commit	Filename
-	Microsoft Azure Storage Account Key	a2119cc	test/integration/config-azblob.yml	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

<sup>🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!</sup>