-
Notifications
You must be signed in to change notification settings - Fork 345
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
Sourceless Integration status show default provider/version #5309
Comments
squakez
added a commit
to squakez/camel-k
that referenced
this issue
Apr 17, 2024
... for external kit or syntetic Integrations. As a side effect, we had to introduce a further check to avoid leveraging a Camel catalog which was taken as default. Closes apache#5309
squakez
added a commit
to squakez/camel-k
that referenced
this issue
Apr 19, 2024
... for external kit or syntetic Integrations. As a side effect, we had to introduce a further check to avoid leveraging a Camel catalog which was taken as default. Closes apache#5309
squakez
added a commit
to squakez/camel-k
that referenced
this issue
Apr 23, 2024
... for external kit or syntetic Integrations. As a side effect, we had to introduce a further check to avoid leveraging a Camel catalog which was taken as default. Closes apache#5309
squakez
added a commit
that referenced
this issue
Apr 23, 2024
... for external kit or syntetic Integrations. As a side effect, we had to introduce a further check to avoid leveraging a Camel catalog which was taken as default. Closes #5309
squakez
added a commit
to squakez/camel-k
that referenced
this issue
Apr 23, 2024
... for external kit or syntetic Integrations. As a side effect, we had to introduce a further check to avoid leveraging a Camel catalog which was taken as default. Closes apache#5309
squakez
added a commit
that referenced
this issue
Apr 24, 2024
... for external kit or syntetic Integrations. As a side effect, we had to introduce a further check to avoid leveraging a Camel catalog which was taken as default. Closes #5309
squakez
added a commit
to jboss-fuse/camel-k
that referenced
this issue
Apr 24, 2024
... for external kit or syntetic Integrations. As a side effect, we had to introduce a further check to avoid leveraging a Camel catalog which was taken as default. Closes apache#5309 (cherry picked from commit apache/camel-k@3e7006887)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Running a sourceless Integration always report the default provider and the default runtime version:
The text was updated successfully, but these errors were encountered: