Uploaded image for project: 'Docs for Red Hat Developers'
  1. Docs for Red Hat Developers
  2. RHDEVDOCS-2091

[srvls] Enhance Event Source creation flow to include ability to create Camel K connectors

    XMLWordPrintable

Details

    • Story
    • Resolution: Won't Do
    • Minor
    • None
    • OpenShift 4.6 Async
    • Developer Console
    • 3
    • Documentation (Ref Guide, User Guide, etc.), User Experience

    Description

      ODC epic: https://issues.redhat.com/browse/ODC-4230

      Description

      As a user, I want to create the top 8 priority Connectors as part of the Event Source creation flow.

      Acceptance Criteria

      1. Document creation of Camel K connectors as part of Event Source creation: https://docs.openshift.com/container-platform/4.5/serverless/event_sources/knative-event-sources.html#creating-event-sources 

      Attachments

        Issue Links

          documents

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. ODC-4067 Catalog experience for Event Sources

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          relates to

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. RHDEVDOCS-1561 Creating and deleting Knative eventsources

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. RHDEVDOCS-3110 [srvls] Document support for community Kamelets in event source catalog

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Activity

            People

              Unassigned Unassigned
              pchandra@redhat.com Preeti Chandrashekar
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: