Selfhosted

38746 readers

860 users here now

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).
No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Automated CI/CD Data Snapshots (lemmy.ml)

submitted 2 months ago by rhymepurple@lemmy.ml to c/selfhosted@lemmy.world

4 comments fedilink hide all child comments

cross-posted from: https://lemmy.ml/post/16693054

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 viewing a single comment's thread
view the rest of the comments

[–] vvv@programming.dev 2 points 2 months ago (1 children)

Are you using PersistentVolumes? If your storage class supports it, looks like there's a volume snapshot concept you can use, have you looked into that?

[–] rhymepurple@lemmy.ml 1 points 2 months ago

Yes, I am using PersistentVolumes. I have played around with different tools that have backup/snapshot abilities, but I haven't seen a way to integrate that functionality with a CD tool. I'm sure if I spent enough time working through things, I may be able to put together something that allows the CD tool to take a snapshot. However, I think that having it handle rollbacks would be a bit too much for me to handle without assistance.