Loading custom library not working when listing files individually about ytt

[guludo]

Yes.

[cppforlife]

@guludo right, when loading individual files they all get their "basename" file names. e.g.

$ ytt -f examples/eirini/config-alt1.yml -f examples/eirini/config.lib.yaml --files-inspect
config-alt1.yml
config.lib.yaml

this was done because there is no obvious way to normalize cases such as ../../config.lib.yml and https://something.com/something.yml except with the current approach. this might be surprising though.

in your example you would have to load directory that contains _ytt_lib via -f .

[guludo]

I see. That makes sense. Additionally to the examples you showed, it would also be hard to know the the "root" directory intended by the user...

I think two things could be done regarding documentation then:

1. Fix documentation on load(), by removing or changing the following: "equivalently, ytt -f app1.yml -f helpers.lib.yml -f _ytt_lib/apps/apps.lib.yml will also make above possible".
2. Make clear the different semantics of -f. That is:
   i. when the argument is a file, ytt adds only the file name to its internal "file list";
   ii. then the argument is a directory, the files under it are added as paths relative to that directory.

Does that make sense?

[cppforlife]

👍 on both.

[nimakaviani]

@guludo would you be willing to send in a PR?

[nimakaviani]

closing.