knockknock10 commented on issue #6936: URL: https://github.com/apache/camel-k/issues/6936#issuecomment-6710905996
I was looking at `KnativeRefBindingProvider` and `knativeTrait`, and noticed that the Pipe binding still depends on the trait for quite a bit of the actual work. The provider maps the references to `knative:event`, `knative:channel` and `knative:endpoint`, but the trait is still responsible for setting up the environment and creating resources like Triggers and Subscriptions. So simply changing the URI mapping won't really solve the problem. @squakez Would it make sense to move that resource setup into the Pipe binding flow itself, instead of keeping it tied to the deprecated trait? I'd also want to keep the Serving Service handling separate, since the earlier deprecation issue says that part should remain unchanged. Curious whether this is close to what you had in mind for #6936. -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
