UchihaIthachi opened a new issue, #6932: URL: https://github.com/apache/camel-k/issues/6932
### Requirement The KEDA trait discovers scaling settings automatically for Kafka and Artemis sources. I'd like the same for the Camel `pulsar:` component, so a route consuming `pulsar:persistent://tenant/ns/topic` scales on the subscription backlog without writing the trigger by hand. There is no Pulsar mapper in `pkg/trait/keda/scalers` yet, so with `keda.auto=true` a Pulsar consumer gets no trigger. Proposal: add a `pulsar` ScaleMapper for the KEDA `pulsar` scaler: - `topic`: from the endpoint path - `subscription`: `subscriptionName` param, then `camel.component.pulsar.subscription-name`, then Camel's default `subs` - `adminURL`: built from `serviceUrl` / `camel.component.pulsar.service-url` (`pulsar://host:6650` -> `http://host:8080`), the same way the Artemis mapper derives its management endpoint from the integration properties With unit tests and an e2e test in the KEDA workflow using a Pulsar standalone Deployment + Service. I have it ready and will open the PR right away. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
