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

Interactive mode for creating operator backed service #2799

Closed
1 task
dharmit opened this issue Apr 2, 2020 · 8 comments
Closed
1 task

Interactive mode for creating operator backed service #2799

dharmit opened this issue Apr 2, 2020 · 8 comments
Labels
kind/user-story An issue of user-story kind lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. v2 Issue or PR that applies to the v2 of odo

Comments

@dharmit
Copy link
Member

dharmit commented Apr 2, 2020

/kind user-story

User Story

As a user I want to interactively create an operator backed service so that I can provide the value to various parameters.

Acceptance Criteria

  • odo service create command, which already takes you to interactive mode to start services based on Service Catalog, should also allow users to interactively create services from operators

Links

/kind user-story

@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci-robot openshift-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 1, 2020
@dharmit dharmit removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 2, 2020
@girishramnani
Copy link
Contributor

Would you be able to complete this for v2 @dharmit ?

@dharmit
Copy link
Member Author

dharmit commented Jul 3, 2020

No, I don't think this would be possible to do for v2. 2.1.0 might be a good target for this.

@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci-robot openshift-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 25, 2020
@dharmit dharmit removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 17, 2020
@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci-robot openshift-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 15, 2021
@dharmit
Copy link
Member Author

dharmit commented Feb 16, 2021

/lifecycle frozen

@openshift-ci-robot openshift-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Feb 16, 2021
@kadel
Copy link
Member

kadel commented Feb 6, 2023

Creating operator-backed services was intentionally removed from odo v3.

#5523 can be used as tracking issue I case we at some point decide to add it back

/close

@openshift-ci openshift-ci bot closed this as completed Feb 6, 2023
@openshift-ci
Copy link

openshift-ci bot commented Feb 6, 2023

@kadel: Closing this issue.

In response to this:

Creating operator-backed services was intentionally removed from odo v3.

#5523 can be used as tracking issue I case we at some point decide to add it back

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

@rm3l rm3l added the v2 Issue or PR that applies to the v2 of odo label Jun 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/user-story An issue of user-story kind lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. v2 Issue or PR that applies to the v2 of odo
Projects
Archived in project
Development

No branches or pull requests

6 participants