-
Sub-task
-
Resolution: Done
-
Normal
-
None
-
None
-
None
-
False
-
-
False
-
Unset
-
CRCPLAN-232 - AuthZ | PRBAC v2 Service Provider Migration Initiation (Internal)
-
-
-
A&M Tech Debt Q10, Access & Management Sprint 95, Access & Management Sprint 95, Access & Management Sprint 96, Access & Management Sprint 97, Access & Management Sprint 98
The relations sink connector in https://github.com/project-kessel/kafka-relations-sink is built simply by `mvn clean package`. This is fine for local development, where the docker-compose file can pick up the local build in the target folder and mount it as a volume. However, for an OpenShift-based deployment, the artifacts need to be deployed and referenceable at a central location such as maven central. For example, the strimzi docs point to artifact locations in the `KafkaConnect` resources.
We already have a maven central repository for kessel, which members of the rebac team already have access to (you need to send them an email to add people to this namespace!): org.project-kessel. Go to https://central.sonatype.com/publishing/namespaces to view.
Tasks:
- Determine if maven central is the correct location for the sink connector artifact. There's a chance we may need to build and host internally on Red Hat infra (see next point).
- Determine whether we need to build and deploy the artifact using Konflux.
- Assuming maven central is fine, the pom.xml plugin config for deploying there can be taken from https://github.com/project-kessel/relations-client-java/blob/main/pom.xml.
- Deploy a version 0.1 to maven central.
Definition of done:
- Sink connector plugin artifact is referenceable at the correct url for use in deployment specs.