Are dependencies identified?

1. [TODO] Discussion - Immutable secrets solved the issue of Infinite reconcile loop in case of two SBRs sharing an application. Now, that we are dropping support for immutable binding secret, it should be ensured that the infinite reconcile loop problem does not re-appear. There is a acceptance test to cover this scenario.
2. [TODO] Discussion - In the current implementation when service credentials change, a new binding secret is created with a new name (because binding secret content changes). However, to align with the spec, the binding secret should not react to the service credentials change. 

Are blockers noted?

No blockers. 

What is the  expected delivery timeline?

GA

Is design implementable?

1. Update Binding Secret Name to remove the hash prefix.
2. [TODO] Find more design implementation steps. 

What is the acceptance criteria?

1. Existing Acceptance tests will test the scenario.
2. Acceptance test "steps/assertions" have to be updated including this step. 
3. Update Examples. 

Is the story (roughly) estimated?

5