-
Notifications
You must be signed in to change notification settings - Fork 244
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
Comments
A friendly reminder that this issue had no activity for 90 days. Stale issues will be closed after an additional 30 days of inactivity. |
This issue was closed because it has been inactive for 30 days since being marked as stale. |
/reopen |
@rm3l: Reopened this issue. In response to this:
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. |
/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.
The text was updated successfully, but these errors were encountered: