You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What happened?
This is defined in a sub dir devspace file in my project:
dependencies:
- name: chainsource:
path: ../../
With normal devspace dev, this works just fine.
However if you decide to use devspace dev --config foo/bar/devspace.yaml from say the root of my project, the local path of the dependency starts from the working dir of the shell, in this case the root of the project. It does not start from where the sub devspace.yaml file is located within the project.
What did you expect to happen instead?
Local path should still work by beginning its path from where it is located in the project. Not based on the working directory of the shell where you invoked the command.
How can we reproduce the bug? (as minimally and precisely as possible)
Local Environment:
DevSpace Version: [use devspace --version] 5.3.0
Operating System: mac
/kind bug
The text was updated successfully, but these errors were encountered:
What happened?
This is defined in a sub dir devspace file in my project:
With normal devspace dev, this works just fine.
However if you decide to use
devspace dev --config foo/bar/devspace.yaml
from say the root of my project, the local path of the dependency starts from the working dir of the shell, in this case the root of the project. It does not start from where the sub devspace.yaml file is located within the project.What did you expect to happen instead?
Local path should still work by beginning its path from where it is located in the project. Not based on the working directory of the shell where you invoked the command.
How can we reproduce the bug? (as minimally and precisely as possible)
Local Environment:
devspace --version
] 5.3.0/kind bug
The text was updated successfully, but these errors were encountered: