-
Story
-
Resolution: Obsolete
-
Undefined
-
None
-
None
Are dependencies identified?
No dependencies.
Are blockers noted?
No blockers.
What is the expected delivery timeline?
GA
Is design implementable?
- Remove `NamingStrategy` field from Service Binding Spec
- Remove templates related to naming strategy
- Remove other relevant pieces from code related to Naming Strategy.
- 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