Is there a feature in a CI/CD pipeline that creates a snapshot or backup of a service’s data prior to running a deployment? The steps of a ideal workflow that I am searching for are similar to:
CI tool identifies new version of service and creates a pull request
Manually merge pull request
CD tool identifies changes to Git repo
CD tool creates data snapshot and/or data backup
CD tool deploys update
Issue with deployment identified that requires rollback
Git repo reverted to prior commit and/or Git repo manually modified to prior version of service
CD tool identifies the rolled back version
(OPTIONAL) CD tool creates data snapshot and/or data backup
CD tool reverts to snapshot taken prior to upgrade
CD tool deploys service to prior version per the Git repo
(OPTIONAL) CD tool prunes data snapshot and/or data backup based on provided parameters (eg - delete snapshots after _ days, only keep 3 most recently deployed snapshots, only keep snapshots for major version releases, only keep one snapshot for each latest major, minor, and patch version, etc.)
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
