knockknock10 commented on PR #6917: URL: https://github.com/apache/camel-k/pull/6917#issuecomment-6421948962
## Summary Relates to #6910. This design proposal evaluates which connection configuration Camel K can safely reuse when generating KEDA scaler metadata. It distinguishes: - Existing endpoint-URI mapping. - Integration/component property mapping, partially explored in #6893. - A bounded approach for explicitly declared properties of known Kamelets used in Pipes. - Generic connection-bean discovery, source-code scanning and arbitrary reference-graph resolution, which are out of scope for the first iteration. ## Recommendation Preserve existing URI mapping, evaluate statically available Integration/component properties, and investigate explicit mappings for known Kamelet parameters such as `broker-url`. Keep generic connection-bean introspection out of the first iteration. Consider a generic Camel Core configuration-description contract only if a demonstrated, reusable gap remains. ## Scope This PR updates `proposals/keda-connection-beans.adoc` only. No implementation or API changes are included. Feedback is welcome on the feasibility boundaries and the proposed Pipe/Kamelet mapping approach. ## Related work - #6910 — Connection-bean discovery for KEDA scalers - #6893 — ArtemisQueue scaler mapping - #6890 — ArtemisQueue KEDA scaler -- 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]
