Uploaded image for project: 'Service Binding'
  1. Service Binding
  2. APPSVC-1399

Projection Delivery Methods

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • Primaza 0.1
    • Primaza 0.1
    • Service Binding
    • None
    • Projection Delivery Methods
    • False
    • None
    • False
    • Not Selected
    • To Do
    • QE Needed, Docs Needed, TE Needed, Customer Facing, PX Needed

      Problem:

      Make delivery of SEDs configurable at the claim level

      Goal:

      Create an extensible interface that allows SEDs to be deliver to application via different methods.

      Why is it important?

      Use cases

      Demo requirements

      UI requirements

      Acceptance criteria

      Development:
      QE:
      Documentation: Yes/No (needs-docs|upstream-docs / no-doc)
      Upstream: <Inputs/Requirement details: Concept/Procedure>/ Not Applicable
      Downstream: <Inputs/Requirement details: Concept/Procedure>/ Not Applicable
      UI: Yes/No (upstream/downstream/no)

      Dependencies (External/Internal)

      Design Artifacts (Design Doc Template)

      Exploration

      Note

              Unassigned Unassigned
              dperaza@redhat.com David Peraza
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: