-
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
odo push fails for devfile nodejs, if non default project is used #3151
Comments
as discussed on slack with @dharmit, he is using this project to deploy https://github.com/sclorg/nodejs-ex, the default devfile https://github.com/elsony/devfile-registry/blob/master/devfiles/nodejs/devfile.yaml#L25 is project specific, we should make it generic. I tried removing the
|
Closing this since my expectation was incorrect. /close |
@dharmit: Closing 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. |
@dharmit why closed it? devfiles should be generic not project specific. |
I agree. But using a specific devfile from a specific registry is going to be project specific, no? 🤔 |
I think no, at least the common one which we are providing is expected to work with multiple projects. |
Is it common among different component types, i.e., nodejs, java, etc.? And where (which registry) is it available from? |
from common one here i meant not stored in a project repository, no not common for component types, but you should be able to deploy different applications(of same component type) with one devfile. AFAIK devfiles which are supported by odo, should not be project specific i.e the nodejs devfile should be able to work with other nodejs projects too. |
Actually even with s2i components there were a certain conventions that needed to be followed like having a |
This can be closed now, resolved for v2 devfiles Actually for v1 we are expecting a /app folder inside each nodejs app, thus failing for applications that does not have /app folder. /close |
@adisky: Closing 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 bug
What versions of software are you using?
Operating System: all
Output of
odo version
: masterHow did you run odo exactly?
While using a minishift cluster in the backend and having experimental mode enabled, I tried to push a nodejs component.
Actual behavior
Expected behavior
odo push
should have succeeded/priority high
/area devfile
The text was updated successfully, but these errors were encountered: