Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Link via ServiceBindingRequest, part 2 #4590

Closed
4 tasks done
serenamarie125 opened this issue Apr 6, 2021 · 3 comments
Closed
4 tasks done

Link via ServiceBindingRequest, part 2 #4590

serenamarie125 opened this issue Apr 6, 2021 · 3 comments
Labels
estimated-size/M (10-20) Rough sizing for Epics. About 1 sprint of work for one person kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation kind/user-story An issue of user-story kind priority/High Important issue; should be worked on before any other issues (except priority/Critical issue(s)).

Comments

@serenamarie125
Copy link

serenamarie125 commented Apr 6, 2021

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

Good to have

JIRA Epic Tracking

ODO-47

@openshift-ci-robot openshift-ci-robot added the kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation label Apr 6, 2021
@serenamarie125
Copy link
Author

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

@serenamarie125 serenamarie125 added this to the 2.2 (Planning) milestone Apr 6, 2021
@kadel kadel added kind/user-story An issue of user-story kind priority/High Important issue; should be worked on before any other issues (except priority/Critical issue(s)). labels Apr 7, 2021
@dharmit dharmit added the estimated-size/M (10-20) Rough sizing for Epics. About 1 sprint of work for one person label Apr 22, 2021
@dharmit
Copy link
Member

dharmit commented Jul 6, 2021

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

/close

@openshift-ci
Copy link

openshift-ci bot commented Jul 6, 2021

@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.

@openshift-ci openshift-ci bot closed this as completed Jul 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
estimated-size/M (10-20) Rough sizing for Epics. About 1 sprint of work for one person kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation kind/user-story An issue of user-story kind priority/High Important issue; should be worked on before any other issues (except priority/Critical issue(s)).
Projects
None yet
Development

No branches or pull requests

4 participants