"workspace" field isn't relative to yaml; but PWD

[ahmetb]

In skaffold v0.5.0 , it appears like "workspace" field is relative to the directory where the command is run (a.k.a. $PWD) rather than the yaml file.

Is this by design and/or the desired behavior?

For example, if I have a voting-app in my current dir ($PWD) and this yaml at ./skaffold/skaffold.yaml:

  - imageName: vote
    workspace: ../voting-app/vote/

I expect that the workspace will be computed relative to ./skaffold not $PWD(=.).

[nkubala]

I think this was originally by design, but this can actually be a bit confusing, especially because we support passing in a path to a skaffold.yaml which can live anywhere. We should probably support passing in a skaffold workspace to set as the "root" for all other relative paths specified in the skaffold.yaml

[thomas-riccardi]

Other relative paths should probably be changed to be relative to the skaffold.yaml file:

• open Dockerfile: no such file or directory #387
• deploy.kubectl.manifests path relative to what? #501
• probably more

cf #387 (comment)

[balopat]

I agree that this is counter-intutitive but we'll have to be careful not to break people who are already using path resolution the current way. It would be great to have more feedback/support from the community around this.

[mistereechapman]

Its becoming a bit of a mess, a bit more control over the docker file build would be great. <- feed back and support in a line 👍

Skaffold v1.0.0 issue
Even adding the workspace prop on the docker build definition would help us

[tstromberg]

Thank you for the idea!

I'm closing this issue as it's been open a while, and it is not clear if it's still an open issue. No one has recently stated an interest in addressing this, but if you feel strongly about it, please feel free to add a comment or send us a PR!