redhat-developer/odo

Link via ServiceBindingRequest, part 2

serenamarie125 opened this issue · 3 comments

serenamarie125 commented

Description

As a developer, I would like to be able to easily inject my source component with the config/secrets/envvars needed to invoke a backing application, so I can focus on may application code instead of configuring application connections.

Acceptance criteria

  • User can issue link command and then push changes, when pushed it will be determined that the components are compatible for ServiceRequestBinding and perform the function.
  • User can list linked components
  • User can unlink, or remove link.

User Stories

  • odo link should store link information in devfile #4208
  • Suport linking devfile component with another component (#3423)

Good to have

  • Disallow self linking of a component (#1052)
  • Add linked component/service information in odo describe for devfile component and operator services (#3734)

JIRA Epic Tracking

ODO-47

serenamarie125 commented

@dharmit @kadel could you add story points? Thank you

dharmit commented

All User Stories covered including those in "Good to Have".

/close

openshift-ci commented

@dharmit: Closing this issue.

In response to this:

All User Stories covered including those in "Good to Have".

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.