Loading...

XML

Word

Printable

Type: Story
Resolution: Done
Priority: Major
Fix Version/s: None
Affects Version/s: None
Component/s: Core - DBaaS Operator
Labels:
None

Blocked:
False
Ready:
False
Epic Link:
Atlas Database Developer Workflow
Discussed with Team:
No
Release Note Text:
Undefined
Market:

SFDC Cases Links:
SFDC Cases Counter:
SFDC Cases Open:

As a DB/OCP admin, I want DB instances that I have selected via admin workflow exposed as bindable Resources so that developers may use them via developer workflow UX.

blocks

DBAAS-19 Demo PoC of binding imported Atlas instances to application via UX

Closed

causes

DBAAS-14 Research ServiceBindingOperator

Closed

DBAAS-16 add OLM support for dbaas-operator

Closed

DBAAS-21 create DBaaSConnection CRD to serve as bindable resource

Closed

DBAAS-24 create deployment owned by DBaaSConnection for binding

Closed

DBAAS-25 annotate DBaaSConnection for binding (SBO) availability

Closed

DBAAS-28 Add Spec field to AtlasService for dbaas-operator to indicate selected imports

Closed

DBAAS-29 gather Atlas instance connection info and add to AtlasService status

Closed

DBAAS-31 can we change bindAsFiles to false with topology-created bindings?

Closed

DBAAS-34 programmatically create Atlas db user for accessing import instances

Closed

DBAAS-35 update dbaas-operator to consume new created database user info

Closed

(6 causes)

Assignee:: Unassigned

Reporter:: Jeremy Ary

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Created:: 2021/04/29 3:46 PM

Updated:: 2021/10/20 2:10 PM

Resolved:: 2021/05/10 2:17 PM

Details

Description

Attachments

Issue Links

Easy Agile Planning Poker

Activity

People

Dates