squakez commented on issue #6910:
URL: https://github.com/apache/camel-k/issues/6910#issuecomment-6704370940
One additional requirement we can consider for the design of this feature.
Let's consider the following Integration code:
```
spec:
flows:
- beans:
- name: rabbitConnectionFactory
type:
org.springframework.amqp.rabbit.connection.CachingConnectionFactory
properties:
host: my-rabbitmq.my-ns.svc
port: 5672
username: admin
password: admin
- route:
from:
uri: spring-rabbitmq:my-exchange?queues=my-queue&routingKey=my-key
steps:
- to: log:info
traits:
camel:
properties:
-
camel.component.spring-rabbitmq.connection-factory=#rabbitConnectionFactory
```
It could even be Java or XML, but let's use YAML DSL as a reference. In the
scaler mapping we should be able to identify the connection bean name
`#rabbitConnectionFactory`, then, we should be able to scan the code and
identify the bean properties and maybe use those one to automatically configure
the scaler.
@knockknock10 I think this approach may be partially solving the doubts we
were having about the complexity of scanning the registry. We cannot scan at
runtime, but, if we have enough info at build time, then, we should be able to
automatically configure the scaler. WDYT?
--
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]
