Skip to content

Unified Backups: Add gitlab-backup-cli to Omnibus

Unified Backups: Add gitlab-backup-cli to Omnibus

- Adds wrapper around `gitlab-backup-cli` command
- Adds recipe and template for `gitlab-backup-cli` yaml configuration

Closes https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/8273

Changelog: added

This MR creates a software and recipe for gitlab-backup-cli tool that unifies backups. For more context, please check: &11908

The main idea is to share the variables that the tool needs from the Omnibus project to perform the backup and restore processes and ensure that the necessary permissions are granted.

Related issues

#8273 (closed)

Checklist

See Definition of done.

For anything in this list which will not be completed, please provide a reason in the MR discussion.

Required

  • MR title and description are up to date, accurate, and descriptive.
  • MR targeting the appropriate branch.
  • Latest Merge Result pipeline is green.
  • When ready for review, MR is labeled "~workflow::ready for review" per the Distribution MR workflow.

For GitLab team members

If you don't have access to this, the reviewer should trigger these jobs for you during the review process.

  • The manual Trigger:ee-package jobs have a green pipeline running against latest commit.
  • If config/software or config/patches directories are changed, make sure the build-package-on-all-os job within the Trigger:ee-package downstream pipeline succeeded.
  • If you are changing anything SSL related, then the Trigger:package:fips manual job within the Trigger:ee-package downstream pipeline must succeed.
  • If CI configuration is changed, the branch must be pushed to dev.gitlab.org to confirm regular branch builds aren't broken.

Expected (please provide an explanation if not completing)

  • Test plan indicating conditions for success has been posted and passes.
  • Documentation created/updated.
  • Tests added.
  • Integration tests added to GitLab QA.
  • Equivalent MR/issue for the GitLab Chart opened.
  • Validate potential values for new configuration settings. Formats such as integer 10, duration 10s, URI scheme://user:passwd@host:port may require quotation or other special handling when rendered in a template and written to a configuration file.

Closes #8273 (closed)

Edited by Robert Marshall

Merge request reports

Loading