Project

General

Profile

Actions
Copy link

action #64123

closed

Expose database revert as a manual trigger

Added by livdywan over 4 years ago. Updated about 4 years ago.

Status:
Rejected
Priority:
Low
Assignee:
livdywan
Category:
-
Target version:
QA - future
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.

Actions
Copy link
 #1

Updated by okurz about 4 years 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".

Actions
Copy link
 #2

Updated by okurz about 4 years 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.

Actions
Copy link

Also available in: Atom PDF