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.

Sign up for GitHub

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

Jump to bottom

Container component restriction should be contained to odo dev #7162

Open
3 tasks
michael-valdron opened this issue Dec 7, 2023 · 2 comments
Open
3 tasks

Container component restriction should be contained to odo dev #7162

michael-valdron opened this issue Dec 7, 2023 · 2 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. needs-triage Indicates an issue or PR lacks a `triage/*` and requires one.

Comments

@michael-valdron
Copy link
Member

/kind user-story

User Story

As a developer, I want to use odo deploy on outerloop devfiles, so that I can deploy my application using devfile k8s resources without needing a container component.

Currently, there is a restriction on all odo commands to require a container component in order to run them. With the existence of outerloop devfiles this restriction should only apply to odo dev, which needs a container component to run the innerloop setup.

Acceptance Criteria

  • Container component should be required when running odo dev
  • Container component should not be required for other odo commands
  • Any documentation or testing tied to these changes should be updated

Links

  • Related Epic (mandatory): N/A

/kind user-story
@openshift-ci openshift-ci bot added the kind/user-story An issue of user-story kind label Dec 7, 2023
@github-actions github-actions bot added the needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. label Dec 7, 2023
@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Mar 7, 2024

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 Mar 7, 2024
@rm3l
Copy link
Member

rm3l commented Mar 8, 2024

/remove-lifecycle stale
/lifecycle frozen

@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 Mar 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
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. needs-triage Indicates an issue or PR lacks a `triage/*` and requires one.
Projects
odo Project
Status: No status
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rm3l @michael-valdron