EPIC Goal

What are we trying to solve here?

As an RHDH user, I want to be able to rollback /restore my application to a previous state, so that I can continue to use the application in case of critical issues discovered after upgrading it.

Background/Feature Origin

See Slack thread: https://redhat-internal.slack.com/archives/C04CUSD4JSG/p1719337051287219

Right now, rollbacks are not possible (with either Helm or the Operator) due to Backstage database migrations not working when Backstage is downgraded (see https://github.com/backstage/backstage/issues/22439).

Since taking regular database backups should be a recommended practice, we want to give guidance on how to perform a rollback using an existing DB backup.

Why is this important?

Users will probably need to rollback should we have a critical issue (like the last-minute https://issues.redhat.com/browse/RHIDP-2931) discovered.

User Scenarios

Dependencies (internal and external)

Acceptance Criteria

• Document how to perform a rollback via Helm using an existing database backup
• Document how to perform a rollback via the Operator using an existing database backup
• Test both scenarios (QE)

Release Enablement/Demo - Provide necessary release enablement details
and documents

DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
Issue>

DEV - Upstream documentation merged: <link to meaningful PR or GitHub
Issue>

DEV - Downstream build attached to advisory: <link to errata>

QE - Test plans in Playwright: <link or reference to playwright>

QE - Automated tests merged: <link or reference to automated tests>

DOC - Downstream documentation merged: <link to meaningful PR>