knockknock10 opened a new pull request, #6917: URL: https://github.com/apache/camel-k/pull/6917
## Summary Relates to #6910. This proposal evaluates how Camel K could discover connection configuration declared outside Camel endpoint URIs and use the available information when generating KEDA scaler metadata. It covers: - The current KEDA scaler discovery and mapping flow. - The limitations of resolving component properties and connection beans. - Possible approaches within Camel K and the feasibility of a generic metadata contract in Camel Core. - Compatibility, security, and testing considerations. ## Recommendation Start by evaluating statically available Integration properties and common declarative bean configurations. If Camel K cannot reliably resolve the required configuration, assess a generic Camel Core metadata contract. Automatic discovery should remain deterministic and must not instantiate arbitrary application beans or expose credentials in plaintext KEDA metadata. ## Scope This PR contains **design documentation only** in `proposals/keda-connection-beans.adoc`. No implementation or API changes are included. Feedback is welcome on the proposed approach, its limitations, and whether the problem can be adequately addressed in Camel K or requires further investigation in Camel Core. ## Related issues and PRs - #6910 — Design a possible way to discover and use connection beans in 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]
