Camel K already parses import dependencies from source in order to calculate the required dependencies. We should extend this behavior to properties in order to be able to calculate dependencies that may be implicitly included by adding some Camel configuration property (ie, the secret managers configuration, the master component, the metrics, ...).
Camel K already parses import dependencies from source in order to calculate the required dependencies. We should extend this behavior to properties in order to be able to calculate dependencies that may be implicitly included by adding some Camel configuration property (ie, the secret managers configuration, the master component, the metrics, ...).