astefanutti opened a new issue #1616:
URL: https://github.com/apache/camel-k/issues/1616
While the trait configuration could be structured and hierarchical, it is
currently limited by the _flat_ CLI used for trait configuration. For example,
if hierarchical CLI would be supported, it would be possible to execute:
$ kamel run -t route.tls.termination=... -t route.tls.certificate=... -t
route.tls.key=...
Instead of:
$ kamel run -t route.tls-termination=... -t route.tls-certificate=... -t
route.tls-key=...
The major benefit would be that Kubernetes/OpenShift API types could be
reused directly, i.e. in that example `TLSConfig`.
Also, the configuration, serialised into the `Integration`, `IntegrationKit`
and `IntegrationPlatform` would be structured, hence more legible.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
