You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we use a Kamelet, we may be in the situation to apply certain configuration to the KameletBinding in order to properly use it. For instance, when we use the predicate-filter-action we need to apply some build time configuration such as:
I am wondering if we should include some mechanism to let all KameletBindings using a Kamelet to inherit some configuration (ie, traits) needed by the Kamelet.
The text was updated successfully, but these errors were encountered:
For this particular case I believe the problem should be addressed in camel-k runtime or camel-quarkus as kamelets are not more a camel-k only feature so introducing some runtime specific bits to a kamelet would probably be not the best option
This issue has been automatically marked as stale due to 90 days of inactivity.
It will be closed if no further activity occurs within 15 days.
If you think that’s incorrect or the issue should never stale, please simply write any comment.
Thanks for your contributions!
When we use a
Kamelet
, we may be in the situation to apply certain configuration to theKameletBinding
in order to properly use it. For instance, when we use thepredicate-filter-action
we need to apply some build time configuration such as:I am wondering if we should include some mechanism to let all KameletBindings using a Kamelet to inherit some configuration (ie, traits) needed by the Kamelet.
The text was updated successfully, but these errors were encountered: