microcks / microcks/microcks-operator
Configmap without `kube.mp.messaging.incoming.microcks-asyncapi-triggers.bootstrap.servers` key on version 1.14
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 14
- Forks
- 13
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 14
Description
### Describe the bug
The config map for async is created without the value
kube.mp.messaging.incoming.microcks-asyncapi-triggers.bootstrap.servers
on version 1.14.0
### Expected behavior
kube.mp.messaging.incoming.microcks-asyncapi-triggers.bootstrap.servers set to Kafka cluster created by microcks installation
### Actual behavior
_No response_
### How to Reproduce?
### Microcks version or git rev
1.14
### Install method (`docker-compose`, `helm chart`, `operator`, `docker-desktop extension`,...)
Operator on openshift
### Additional information
_No response_
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing a Microcks 1.14 operator installation on OpenShift and inspecting the generated ConfigMap for the async trigger configuration. Trace where the operator assembles kube.mp.messaging.incoming.microcks-asyncapi-triggers.bootstrap.servers and compare it with the Kafka cluster created by the installation. Done means the key is present and points to that cluster.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, kafka, kubernetes
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100