Story (Required)

As a user, I would like to understand how to create binding between a service and an application.

Background (Required)

A user would like to understand how to bind a service to an application and what to do in particular use cases.

Out of scope

Any new examples demonstrating the end-to-end usage.

In Scope

A Section in the user guide.

Approach(Required)

• Start with simple examples first, e.g. service bindings that just refer a service and application, explain defaults, highlight differences if any between our and spec API.

• For each non-default option, explain what is the use case for it and when a user should use it, e.g.
  • when to change binding path
  • when to change injection approach (env vs. files)
  • how to bind to application with an unknown name
  • why and how to create bindings not provided by the service (i.e. mappings)
  • why and how change binding names (naming strategies)
  • what if binding data are spread across multiple service resources?
  • try to structure the content in problem-oriented/FAQ style

Also:

• mandatory bindings and how specify them if missing on service
• how to interpret binding status? What useful information can be found there?
• mention that successful service binding are immutable
• service binding removal
• refer service binding spec where appropriate
• highlight difference between our and spec api where appropriate

Acceptance Criteria

A section in the user guide addressing topics listed in "Approach"

INVEST Checklist

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

Legend

Unknown
Verified
Unsatisfied