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

A new command to add K8s component to the Devfile from file #6338

Open
valaparthvi opened this issue Nov 23, 2022 · 4 comments
Open

A new command to add K8s component to the Devfile from file #6338

valaparthvi opened this issue Nov 23, 2022 · 4 comments
Labels
kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. priority/Low Nice to have issue. It's not immediately on the project roadmap to get it done.

Comments

@valaparthvi
Copy link
Contributor

/kind feature

Which functionality do you think we should add?

Add a new command to odo that will add K8s component to the Devfile from a file.

odo add component --type k8s --from-file <file>

Why is this needed?

This command might be helpful in cases where you need to modify the Devfile to add a K8s resource without doing so manually.
For e.g., defining a DB microservice inside Devfile that the application can connect to via ServiceBinding; odo will ensure the microservice is created for a successful bind.
Using the command will avoid having to use kubectl or oc client to create the service as well.

@openshift-ci openshift-ci bot added the kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation label Nov 23, 2022
@rm3l rm3l added this to odo Project Nov 23, 2022
@github-actions github-actions bot added the needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. label Nov 23, 2022
@valaparthvi
Copy link
Contributor Author

cc: @mohitsuman
I am opening this issue after my discussion with Tomas about his discussion with you. This command might help with your guides.

@github-actions
Copy link
Contributor

A friendly reminder that this issue had no activity for 90 days. Stale issues will be closed after an additional 30 days of inactivity.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 16, 2023
@github-actions
Copy link
Contributor

This issue was closed because it has been inactive for 30 days since being marked as stale.

@github-actions github-actions bot added the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Aug 17, 2023
@github-project-automation github-project-automation bot moved this to Done ✅ in odo Project Aug 17, 2023
@rm3l rm3l removed the needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. label Sep 7, 2023
@rm3l
Copy link
Member

rm3l commented Oct 30, 2023

/remove-lifecycle rotten
/remove-lifecycle stale
/lifecycle frozen
/priority Low
/reopen

Still relevant.

@rm3l rm3l reopened this Oct 30, 2023
@openshift-ci openshift-ci bot added priority/Low Nice to have issue. It's not immediately on the project roadmap to get it done. and removed lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. labels Oct 30, 2023
@github-project-automation github-project-automation bot moved this from Done ✅ to To Do 📝 in odo Project Oct 30, 2023
@openshift-ci openshift-ci bot 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 Oct 30, 2023
@rm3l rm3l removed the status in odo Project Oct 30, 2023
@github-actions github-actions bot added the needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. label Oct 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. priority/Low Nice to have issue. It's not immediately on the project roadmap to get it done.
Projects
Status: No status
Development

No branches or pull requests

2 participants