pkalsi97 opened a new pull request, #6418:
URL: https://github.com/apache/camel-k/pull/6418

   This PR implements automatic discovery of KEDA triggers from Camel 
integration source URIs. 
   Closes #6312
   #### Changes
   - Adds Camel-to-KEDA mappings and URI parsing functions
   - Adds Unit tests for mappings
   - E2E test fixture (e2e/kafka/files/keda-kafka-auto-discovery.yaml)
   - Added `Auto` bool field in keda trait
   - Added `autoDiscoverTriggers()` method, updated `Configure()`
   - Added auto-discovery integration tests
   - Added E2E test & `ScaledObject()` helper, registered keda.sh API group
   
   #### When the KEDA trait is enabled:
   The system automatically extracts component information from `from()` URIs 
and generates corresponding KEDA ScaledObject triggers without requiring manual 
trigger configuration.
   
   #### Behaviour:
   - **Default**: Auto-discovery is enabled (`auto: true`) when no manual
     triggers are specified
   - **Precedence**: Manually configured triggers always take precedence
     over auto-discovered ones
   - **Opt-out**: Set `keda.auto: false` to disable auto-discovery
   
   #### Supported Components
   | Camel Component   | KEDA Scaler      | Mapped Parameters                   
  |
   
|-------------------|------------------|---------------------------------------|
   | kafka             | kafka            | topic, bootstrapServers, 
consumerGroup|
   | aws2-sqs          | aws-sqs-queue    | queueURL, awsRegion                 
  |
   | spring-rabbitmq   | rabbitmq         | queueName, host                     
  |
   
   #### Example
   ```
   traits:
     keda:
       enabled: true
       # triggers auto-discovered from: 
kafka:my-topic?brokers=my-kafka:9092&groupId=my-group
   ``` 


-- 
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]

Reply via email to