-
Notifications
You must be signed in to change notification settings - Fork 243
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
Instantiate and manage services through Operator #2613
Comments
/assign @dharmit @girishramnani |
a high level thought process around this was -
so a user can provide values while creating the CRD e.g. |
I would prefer the other way around. The operator's name is basically the service name. So the command should be
|
This makes sense and I'm not suggesting that it's a wrong idea, but to keep things in sync with how we do it right now with services and plans (Service Catalog), I'd prefer |
@kadel @girishramnani last two points talk about |
we decided to do |
It's not about when to do it. I understand that it's not essential right now. I'm pointing to there being no |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
/lifecycle frozen |
We have completed all ACs this epic hence closing |
User Story
As a user, I want to create a new instance of my database or another service managed by operators So that I can use it (link it) with my application
Acceptance Criteria
odo service create
command (Instantiate an operator backed service using yaml file #2723)odo service list
should list all created services (odo should list services created from operator #2790)odo service list -o json
should list all created services in JSON format (JSON output for operator backed services in the cluster #2791)odo service delete <service-name>
should delete operator backed services (odo should be able to delete operator backed services #2792)odo link <CR-name>/<service-name>
should link the component underpwd
to the specified service name. (Support link command for devfile #2920)odo unlink <CR-name>/<service-name>
should unlink the component underpwd
from specified service name. ("odo unlink" to unlink a devfile component from an Operator backed service #3563)Links
/area service-operators
/area service
The text was updated successfully, but these errors were encountered: