Project

General

Profile

action #64123

Expose database revert as a manual trigger

Added by cdywan about 1 year ago. Updated 10 months ago.

Status:
Rejected
Priority:
Low
Assignee:
Target version:
Start date:
2020-03-03
Due date:
% Done:

0%

Estimated time:

Description

Akin to rollback there should be a trigger to revert the database, which may be necessary in addition to a rollback.

See https://gitlab.suse.de/openqa/osd-deployment/pipelines

This can be considered a nice to have, for completeness, and maybe a learning opportunity.

History

#1 Updated by okurz about 1 year ago

  • Target version changed from Current Sprint to future

Hasn't been updated since a month and wasn't a priority. So I suggest we keep it assigned to you in case you still want to act on it but move to "future".

#2 Updated by okurz 10 months ago

  • Status changed from New to Rejected

We talked about this issue about a month ago and apparently you have not found time since then. That's ok for me but better you keep this "nice idea" in your personal todo list as this isn't important for us to keep in the generic backlog. A long-term better approach might be something like Kubernetes based infrastructure with automatic deployment and monitoring based automatic rollbacks of redundant, replicating instances.

Also available in: Atom PDF