oscerd opened a new issue, #2829:
URL: https://github.com/apache/camel-kamelets/issues/2829

   ## Description
   
   The `sslKeyPassword` property in the Kafka kamelets has `format: password` 
but is missing `x-descriptors: [urn:camel:group:credentials]`. This means UI 
tools (e.g., Kaoto, Hawtio) won't properly group or mask this sensitive field 
alongside other credentials.
   
   ## Affected Files
   
   - `kamelets/kafka-sink.kamelet.yaml` — `sslKeyPassword` property
   - `kamelets/kafka-source.kamelet.yaml` — `sslKeyPassword` property
   - `kamelets/kafka-batch-source.kamelet.yaml` — `sslKeyPassword` property
   
   ## Steps to Reproduce
   
   1. Open any of the affected kamelet YAML files
   2. Find the `sslKeyPassword` property definition
   3. Observe it has `format: password` but no `x-descriptors` field
   
   ## Expected Behavior
   
   All credential/password properties should include both `format: password` 
and the `x-descriptors` annotation, consistent with how other kamelets handle 
sensitive fields:
   
   ```yaml
   sslKeyPassword:
     title: SSL Key Password
     description: The password of the private key in the key store file.
     type: string
     format: password
     x-descriptors:
       - urn:camel:group:credentials
   ```
   
   ## Actual Behavior
   
   The `sslKeyPassword` property is missing `x-descriptors`:
   
   ```yaml
   sslKeyPassword:
     title: SSL Key Password
     description: The password of the private key in the key store file.
     type: string
     format: password
   ```
   
   ## Additional Context
   
   - Other kamelets (e.g., `ftp-sink`, `mysql-sink`, `aws-s3-sink`) correctly 
include both `format: password` and `x-descriptors: 
[urn:camel:group:credentials]` on their credential properties
   - Target release: **4.21.0**


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