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

Drop support for Naming Strategy

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Obsolete
    • Icon: Undefined Undefined
    • None
    • None
    • Service Binding

      Are dependencies identified?

      No dependencies.

      Are blockers noted?

      No blockers. 

      What is the  expected delivery timeline?

      GA

      Is design implementable?

      1. Remove `NamingStrategy` field from Service Binding Spec
      2. Remove templates related to naming strategy
      3. Remove other relevant pieces from code related to Naming Strategy.
      4. Update User doc and examples.

      What is the acceptance criteria?

      1. Remove custom naming strategy feature -> https://github.com/redhat-developer/service-binding-operator/blob/master/test/acceptance/features/bindWithCustomNamingStrategies.feature

      2. Existing acceptance tests have to be updated to ensure the case is preserved and contains no prefix. For example, the assertions for this acceptance test have to be updated from

      And The application env var "BACKEND_USERNAME" has value "AzureDiamond"
      And The application env var "BACKEND_PASSWORD" has value "hunter2"
      

      to

      And The application env var "username" has value "AzureDiamond" And The application env var "BACKEND_PASSWORD" has value "hunter2"
      And The application env var "password" has value "hunter2"
      

      Is the story (roughly) estimated?

      5

       

              Unassigned Unassigned
              dshikhar Dhriti Shikhar (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: