-
Epic
-
Resolution: Won't Do
-
Undefined
-
None
-
None
-
None
-
[Spike] Investigate customer configuration with Backstage and Google Spanner
-
S
-
False
-
-
False
-
-
Done
-
RHIDP-6017 - Add support for Google Cloud Spanner database
-
QE Needed, Docs Needed, TE Needed, Customer Facing, PX Needed
-
0% To Do, 0% In Progress, 100% Done
-
Release Note Not Required
-
-
EPIC Goal
What are we trying to solve here?
As commented out in https://issues.redhat.com/browse/RHIDP-6017?focusedId=26908764&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-26908764, the first step here would be to set up a call with the customer and the field to understand what they did exactly to have a working instance of Backstage (upstream) backed by Google Cloud Spanner, and try to replicate it with RHDH.
Based on that call and POC, we would be able to create follow-up Epics/stories/tasks to support Spanner as a DB.
Background/Feature Origin
Why is this important?
User Scenarios
Dependencies (internal and external)
Acceptance Criteria
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>
