You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by "squakez (via GitHub)" <gi...@apache.org> on 2024/03/19 10:25:16 UTC

[I] Simplify Vaults addons [camel-k]

squakez opened a new issue, #5258:
URL: https://github.com/apache/camel-k/issues/5258

   ### Requirement
   
   Right now we have the implementation of different vaults configuration in separate addons. Leveraging the draft work proposed in [1] and [2] we may simplify the management of vaults in a single trait in the following manner.
   
   The catalog part would be like the following:
   ```
     capabilities:
         vault:
           hashicorp:
             runtimeProperties:
             - key: host
               value: camel.vault.hashicorp.host
             ...
           aws:
             runtimeProperties:
             - key: region
               value: camel.vault.aws.region
             ...
   ```
   The logic on operator side would be an iteration over the required Camel properties driven by the catalog, whichever they are, making the maintenance a mere check that the given parameter exists in the catalog or not.
   The user experience would be simpler as the user would be using the same trait but with a different provider every time needed. It would be something like:
   
   ```
   kamel run test.yaml -t vault.aws.region=xyz ...
   kamel run test.yaml -t vault.vault.host=my-host ...
   ```
   
   [1] https://github.com/apache/camel-k-runtime/pull/1185
   [2] https://github.com/apache/camel-k/pull/5251
   
   ### Problem
   
   x
   
   ### Proposal
   
   _No response_
   
   ### Open questions
   
   _No response_


-- 
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: commits-unsubscribe@camel.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org