-
Story
-
Resolution: Unresolved
-
Critical
-
None
-
None
-
False
-
None
-
False
Collaborators: Brie for App Studio, Kevin and Stacey for Catalog, Alessandro Tiffany and Amy for Services, Andy Braren for API Explorer
NOTE: we may start with adding DBaaS initially.
As an app dev who got my app running on Red Hat's Cloud in 2 minutes, I want to see what other services are available to me and connect one to my app.
As an app architect, I need to make certain services available to certain workspaces for my development team to use.
Design
- Part of Horizon UX prototype
Notes
- Subscribing to services in Marketplaces deck
- Use Kafka and MongoDB Atlas to start, since they'll be the first connectable services in "App Studio"
- How do service bindings work in this world? Today Managed Kafka requires the service binding operator to be able to use Managed Kafka.
- Consider pulling in RHODA as well?
Suggested sub-tasks
- As a group, collect any “post-MVP” ideas you remember from stakeholder discussions or existing mockups into either this Miro or the E2E Prototype Sketch file
- As a group, identify the key capabilities and flows to include, and any likely connections to other areas of the prototype
- Add and connect things in the Sketch prototype and use #wg-hybrid-console-ux to discuss connections, ask questions, and collaborate async if needed
Journey brainstorming
- Managed Kafka or MongoDB (slide 14 of vision deck)
- Workspace could have a pointer to explore Kafka's API within the API Explorer, integrate that right there
- A unified Catalog page "App Store" with everything in it (rough example) - our managed services, operators, templates of stuff, etc.
- The user can pay for the service in a variety of ways: using a company account, using their own credit card, using a cloud provider marketplace account (Kevin's mockup could be used as a base)
- relates to
-
PD-1400 (HAC Ecosystem) Workspace details page ("Phase 2")
- Closed