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

--config flag: Dependency local path starts from working dir of shell #1226

Closed
harryttd opened this issue Nov 23, 2020 · 1 comment · Fixed by #1228
Closed

--config flag: Dependency local path starts from working dir of shell #1226

harryttd opened this issue Nov 23, 2020 · 1 comment · Fixed by #1228
Assignees
Labels
area/config Issues related to the config kind/bug Something isn't working

Comments

@harryttd
Copy link
Contributor

What happened?
This is defined in a sub dir devspace file in my project:

dependencies:
  - name: chain
    source:
      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

@FabianKramm
Copy link
Collaborator

@harryttd thanks for reporting this issue! Yes this is a bug, we'll fix that!

@FabianKramm FabianKramm added area/config Issues related to the config kind/bug Something isn't working labels Nov 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/config Issues related to the config kind/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants