vendir support for "dot" paths without conflict #244
Labels
carvel-accepted
This issue should be considered for future work and that the triage process has been completed
enhancement
This issue is a feature request
Describe the problem/challenge you have
vendir's requirement that paths do not overlap makes it difficult, or impossible, to create a directory structure that custom ytt modules can be found in if there are also environment specific yamls which need to be included.
consider the following.
The final directory structure that we're looking to create wants to look like this
The above directory layout does not seem to be possible due to a constraint in vendir;
Expected to not manage overlapping paths: 'config/modules' and 'config'
The vendir.yml file we're making using of looks roughly like the following.
the first blob is the blob at issue because it wants to add content to ".", but "." conflicts with the overlay constraint.
Describe the solution you'd like
I'd like vendir to allow this use case similar to how
gilt
allows it. For example, the followinggilt
configuration produces the desired result.but gilt itself has its own constraints in terms of functionality. constraints that vendir doesnt have.
Anything else you would like to add:
part of the issue here, as far as I understand things, has to do with the
ytt
requirement that the_ytt_lib
directory must be a sibling of any yaml files that use content in that directory.If this
ytt
constraint did not exist, then there would be a clear path forward in how to use vendir. We could create any number of sub-directories and then ytt could either be told where it's_ytt_lib
is, or,ytt
could walk up the tree until it found a suitable_ytt_lib
to use.Vote on this request
This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.
👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"
We are also happy to receive and review Pull Requests if you want to help working on this issue.
The text was updated successfully, but these errors were encountered: