-
Story
-
Resolution: Won't Do
-
Undefined
-
None
-
None
-
None
-
False
-
None
-
False
-
-
-
MGDOBR - Sprint 230
Issue Description: this story is for the CRUD of SinkConnectors. RHOSE has to proxy the RHOC api to provision SinkConnectors that the customer can use as destination in their CamelDSL definition
Acceptance Criteria: The user can CRUD SinkConnectors
Out of Scope: SourceConnectors
Additional Information: <Add any additional information here that may be helpful to people reading the ticket>
- relates to
-
MGDOBR-1379 Expose endpoint to retrieve SinkConnectors in the ShardAPI
- Closed
-
MGDOBR-1380 ShardAPI should expose an endpoint to receive the status update from the Shard for the SinkConnectors
- Closed
-
MGDOBR-1384 Implement create SinkConnector user endpoint
- Closed
-
MGDOBR-1385 Implement SinkConnector worker in control plane
- Closed
-
MGDOBR-1386 Add a new table in the database for the Connectors
- Closed
-
MGDOBR-1398 Expose user endpoint to retrieve all the SinkConnectors for a bridge
- Closed
-
MGDOBR-1399 Expose user endpoint to delete a specific SinkConnector
- Closed
-
MGDOBR-1400 Expose user endpoint to get the details of a specific SinkConnector
- Closed
-
MGDOBR-1401 Expose user endpoint to patch a specific SinkConnector
- Closed
-
MGDOBR-1402 Data plane should retrieve all the SinkConnectors resources to be deployed/deleted from the control plane
- Closed
-
MGDOBR-1403 Design the CRD for the SinkConnector and create a controller for that resource
- Closed
-
MGDOBR-1410 Mask secret values in connector's payloads
- Closed
-
MGDOBR-1411 Set KafkaConnection details in SinkConnectorDTO
- Closed