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

support non-standard devfile filename #6600

Open
1 task
kadel opened this issue Feb 16, 2023 · 6 comments
Open
1 task

support non-standard devfile filename #6600

kadel opened this issue Feb 16, 2023 · 6 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. priority/Medium Nice to have issue. Getting it done before priority changes would be great.

Comments

@kadel
Copy link
Member

kadel commented Feb 16, 2023

/kind user-story

User Story

As an odo user, I want to be able to use odo with my project that stores devfile in non-standart path (in subdirectory, or different name than devfile.yaml)

  • So that I don't have to pollute the root of my project with another file.
  • SO that I can have multiple devfiles for alternative workflows.

Acceptance Criteria

  • all odo commands that use devfile.yaml should have --devfile flag that allows user to specify other the default devfile filename

Links

Eclipse Che documentation for custom devfile path https://www.eclipse.org/che/docs/stable/end-user-guide/url-parameter-for-the-devfile-file-path/

/kind user-story
/priority medium
@openshift-ci openshift-ci bot added kind/user-story An issue of user-story kind priority/Medium Nice to have issue. Getting it done before priority changes would be great. labels Feb 16, 2023
@github-actions github-actions bot added the needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. label Feb 16, 2023
@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 Jun 10, 2023
@rm3l rm3l removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 5, 2023
@rm3l
Copy link
Member

rm3l commented Jul 6, 2023 •
edited
Loading

Grooming (Jul 6, 2023)

  • Flag to be added as a global flag (for almost all commands where it makes sense). Not supported for odo analyze
  • Limit the devfile to a sub-directory
  • Ensure consistent behavior regarding .odo
  • Tests should be limited to the simplest cases (like for .devfile.yaml)

@rm3l rm3l removed the needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. label Jul 6, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Oct 5, 2023

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 Oct 5, 2023
@rm3l
Copy link
Member

rm3l commented Oct 5, 2023

/remove-lifecycle stale

Still relevant - related to devfile/api#1035

@openshift-ci openshift-ci bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 5, 2023
@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Jan 4, 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 Jan 4, 2024
@rm3l
Copy link
Member

rm3l commented Jan 4, 2024

/lifecycle frozen
/remove-lifecycle stale

@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 Jan 4, 2024
@rm3l rm3l mentioned this issue Feb 9, 2024
Closed
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. priority/Medium Nice to have issue. Getting it done before priority changes would be great.
Projects
odo Project
Status: No status
Milestone
No milestone
Development

No branches or pull requests
2 participants
@kadel @rm3l