Have option for vendir sync to run in different directory. about vendir HOT 8 CLOSED

To clarify a few scenarios:

Does that line up with what you would expect in this cases?

from vendir.

Hmmm, that seems to complicate things unnecessarily, and doesn't capture the important thing about how relative paths are calculated with -f.

My simple rule would have been that if -c is specified, change to that working directory first before evaluating any other options for paths.

Thus if you use -f as well, then any relative path supplied to it would then be evaluated relative to the directory you changed to.

So:

vendir -c somedir -f relative/path

would be the same as having said:

(cd somedir; vendir -f relative/path)

So yes the table is sort of correct, but misses detail about what happens with relative paths supplied to -f.

from vendir.

do we have some precedent in other tools to do something like this? tar does have -C that does something related.

from vendir.

There's many other tools that support this model as well as many that don't. Is it a requirement that other tools do the same or that is proven to be convenient?

from vendir.

There's many other tools that support this model

im just not familiar with any except tar. do you have some concrete examples (especially for commonly used tools)?

Is it a requirement that other tools do the same

it's not a requirement, but it's definitely an important part of research. id like to see if other tools do it because -C affects all other flags that take in files. it also might be good to understand what makes vendir special as compared to other tools (i hope this wont be a pattern we add to all others). additionally (cd package/foo/bundle; vendir sync) seems like a pretty standard pattern in bash scripts, so adding this feature to eliminate need for subshell seems a bit too special.

from vendir.

im just not familiar with any except tar. do you have some concrete examples (especially for commonly used tools)?

It's not so common because typically tools don't need to work relative to the current directory. Most tools do support specify the root of the "context" of where actions will take place. As an example, kubectl does this when you do kubectl -f dir/sub-dir and many other tools do follow this practice, but since vendir (like any of the other compressing tools, zip, ...) will take current dir as root to use, then they do provide an alternate flag.

Another tool I can think of, as developer that I use is [odo](https://github.com/openshift/odo) that provides 2 flags:

odo create -h 
      --context string                                   Use given context directory as a source for component settings
      --devfile string                                    Path to the user specified devfile

It's not specific that the tool changes directory but that can specify the root of where actions should take place.

(cd package/foo/bundle; vendir sync) is a common pattern that is nice for all those ops people that can do that. tar, zip and all other tools could have done the same pattern, but decided that their users probably didn't need to be advanced enough to know about subshells, etc... Also, providing the functionality from within the tool, prevents different behaviour in different OSes, and simplify scripts.

from vendir.

added --chdir flag: 85f693d. will be included in upcoming release.

from vendir.

included in https://github.com/vmware-tanzu/carvel-vendir/releases/tag/v0.22.0

from vendir.