support overriding directories within pulled dependencies via later directory configs about vendir HOT 4 OPEN

@cppforlife would you say this relates kind of to our use case in #29 ?

from vendir.

nah dont think so. this is more about overriding directories wholesale (with an updated dependency) whereas #29 is more about modifying downloaded dependency. there is some relationship but prolly a bit different.

from vendir.

whereas #29 is more about modifying downloaded dependency.

Oh no, definitely not what I wanted to imply. We don't want to modify any file downloaded. We just want to keep files in the directory tree that did not originate at the source and not have those erased.

from vendir.

We don't want to modify any file downloaded

what i meant is that we see directory represented via a source as a single asset. so any modification to that directory (eg copying over temp files like *.tf.json) is "modifying asset".

from vendir.