-
Story
-
Resolution: Obsolete
-
Undefined
-
None
-
None
-
False
-
False
-
Undefined
-
Are dependencies identified?
No dependencies.
Are blockers noted?
No blockers.
What is the expected delivery timeline?
GA
Is design implementable?
**1. Remove CollectionReady, InjectionReady conditions
What is the acceptance criteria?
- Existing acceptance tests should be updated to remove check for CollectionReady and InjectionReady. Example:
Scenario: Attempt to bind a non existing application to a backend service
Given CustomResourceDefinition backends.stable.example.com is available
* The Secret is present
"""
apiVersion: v1
kind: Secret
metadata:
name: backend-secret
stringData:
username: AzureDiamond
password: hunter2
"""
* The Custom Resource is present
"""
apiVersion: stable.example.com/v1
kind: Backend
metadata:
name: service-missing-app
annotations:
service.binding: path={.status.data.dbCredentials},objectType=Secret,elementType=map
status:
data:
dbCredentials: backend-secret
"""
When Service Binding is applied
"""
apiVersion: binding.operators.coreos.com/v1alpha1
kind: ServiceBinding
metadata:
name: service-binding-missing-app
spec:
bindAsFiles: false
application:
name: gen-missing-app
group: apps
version: v1
resource: deployments
services:
- group: stable.example.com
version: v1
kind: Backend
name: service-missing-app
"""
And jq ".status.conditions[] | select(.type=="Ready").status" of Service Binding "service-binding-missing-app" should be changed to "False"
- Update docs and examples.
Is the story estimated?
3