Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-16119

Think about suppressing direct access to Camel Components in Camel K

XMLWordPrintable

    • Icon: Feature Feature
    • Resolution: Done
    • Icon: Major Major
    • 2021-M3
    • None
    • Camel-K

      The recent upstream discussion [1] sparked a conversation about the support for camel components in Camel K and Camel Quarkus. 

      Long story short, we intend to suppress the use of camel components and want to enforce the use of Camel Quarkus extensions. 

      • How can we accomplish this and improve the user experience ? 
      • What are a users touchpoints where he or she can intentionally or accidentally leave the supported path?

      [1] https://github.com/apache/camel-k/issues/2170

              Unassigned Unassigned
              rhn-support-hbraun Heiko Braun
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: