-
Notifications
You must be signed in to change notification settings - Fork 352
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Data type Kamelet hardcoded #5014
Labels
Milestone
Comments
@christophd fyi |
BTW, this problem is highlighting a compatibility problem we would have in any case as stated in #4395 |
squakez
added a commit
to squakez/camel-k
that referenced
this issue
Jan 24, 2024
squakez
added a commit
to squakez/camel-k
that referenced
this issue
Jan 24, 2024
squakez
added a commit
to squakez/camel-k
that referenced
this issue
Jan 24, 2024
squakez
added a commit
to squakez/camel-k
that referenced
this issue
Jan 24, 2024
squakez
added a commit
that referenced
this issue
Jan 24, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When we make use of data types, we assume the presence of a Kamelet which name is hardcoded [1]. While this could be true most of the time, it may not be the case when the user decide to use a different version of runtime other than the default. I think we need to find a way to have this flexible and give the user the possibility to specify which version of the Data Type action Kamelet wants to use.
[1]
camel-k/pkg/util/bindings/kamelet.go
Line 155 in c8e93fc
The text was updated successfully, but these errors were encountered: