-
Epic
-
Resolution: Done
-
Normal
-
None
-
None
-
Generic managed service flow - phase 1 - topology
-
False
-
False
-
To Do
-
RHDP-324 - Integrating managed cloud services into developer experience
-
0
-
0% To Do, 0% In Progress, 100% Done
-
Undefined
-
M
-
Not Supported
Problem
With the RHOAS Operator, we have introduced a managed service flow. We need to provide a mechanism to support a consistent user flow for all managed services.(Red Hat and non Red Hat)
- topology representation
- support of SBO
Goal
Provide a generic managed service flow which supports Azure & IBM Managed services
Why is it important?
Use cases
- Developer should be able to easily identify any off-cluster items which are part of their application/project via topology
- Developer should be able to easily link off-cluster items with other parts of their application/project
Acceptance criteria
- Display bindable external services in topology as a trapezoid
- Users can create binding connections to any bindable external service
Dependencies (External/Internal)
Design Artifacts
Exploration
Note
- is cloned by
-
ODC-5843 Generic managed service flow - Phase 2
- To Do
- relates to
-
APPSVC-500 Criteria for discovering consumable Services
- Closed
-
APPSVC-848 Enable an available set services of services "Bind-able" with SBO out of the box
- Closed
-
APPSVC-501 Define criteria for detecting bindable services
- Closed
- links to
(1 links to)