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

Display status.binding.name field after data collection is successful

    XMLWordPrintable

Details

    • Story
    • Resolution: Done
    • Undefined
    • SBO 1.2
    • None
    • Service Binding
    • None
    • 5
    • AppSvc Sprint 223

    Description

      Owner: Architect:

      David

      Story (Required)

      As an OCP developer I would like to be able to search for Service Binding Resources bound to a service and referencing a label selector on the workload section, so that I can see the fields that would be projected if I use the labels in my workloads.

      Background (Required)

      See User Experience Doc were the search capability for a developer is explained. For Provisioned Services I can search by going to the service CR referenced in SB CR and then grabbing the secret name from status.binding.name. However, in the case for CRD and CR annotation I would have to relay on status.binding.name on the SB CR itself. The problem is that the status.binding.name field is only available today after the projection step is completed. The ask is to be able to display that field during data collection phase where we already know the fields to project but we have not yet projected those fields cause there is not workloads matching the label selector.

      Glossary

      NA

      Out of scope

      NA

      In Scope

      NA

      Approach(Required)

      We will need to change the code to display status.binding.name at collection time instead of projection time, this small change will give us better service reservation search capabilities. Andy to add more details on the complexity here.

      Dependencies

      None

      Edge Case

      NA

      Acceptance Criteria

      The status.binding.name is visible in the CB CR right after collection status change to done.
      Test case changed to verify that specific scenario.

      INVEST Checklist

      Dependencies identified
      Blockers noted and expected delivery timelines set
      Design is implementable
      Acceptance criteria agreed upon
      Story estimated

      Legend

      Unknown
      Verified
      Unsatisfied

      Attachments

        Activity

          People

            ansadler@redhat.com Andy Sadler
            dperaza@redhat.com David Peraza
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: