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

Copy devfile.yaml dependencies when running odo init with --devfile-path #5713

Open
feloy opened this issue May 5, 2022 · 4 comments
Open
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/Medium Nice to have issue. Getting it done before priority changes would be great.

Comments

@feloy
Copy link
Contributor

feloy commented May 5, 2022

/kind feature

Which functionality do you think we should add?

When a devfile contains dependencies (either a non-inlined Kubernetes component, or a Dockerfile for Image component), running odo init --devfile-path some/devfile.yaml, will copy the devfile.yaml only in the current directory, not the dependencies (YAML manifest for Kubernetes component, Dockerfile, etc).

It would be interesting that odo init also copeies these files, as the devfile.yaml is not usable without them.

Why is this needed?

Per se, the devfile.yaml may not be usable without those referenced files.

@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 May 5, 2022
@kadel kadel added the priority/Medium Nice to have issue. Getting it done before priority changes would be great. label Feb 17, 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 Oct 30, 2023
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 Nov 30, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 30, 2023
@rm3l
Copy link
Member

rm3l commented Mar 5, 2024

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

@openshift-ci openshift-ci bot reopened this Mar 5, 2024
Copy link

openshift-ci bot commented Mar 5, 2024

@rm3l: Reopened this issue.

In response to this:

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

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.

@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. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. labels Mar 5, 2024
@github-actions github-actions bot added the needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. label Mar 5, 2024
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/Medium Nice to have issue. Getting it done before priority changes would be great.
Projects
Status: No status
Development

No branches or pull requests

3 participants