Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

vendir capable of sync'ing files to its current-working-directory #116

Open
caphrim007 opened this issue Oct 7, 2021 · 0 comments
Open
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

Comments

@caphrim007
Copy link

caphrim007 commented Oct 7, 2021

Describe the problem/challenge you have
[A description of the current challenge that you are experiencing.]
i want to compose together a single repo using bits from other repos.

Among those other bits are top-level files like .pre-commit-config.yaml, .tflint, .isort, etc

Describe the solution you'd like
[A clear and concise description of what you want to happen. If applicable a visual representation of the UX.]
When I read the spec of vendir, intuitively it seems like vendir would support this.

for instance,

directories:
- path: .
  contents:
    - path: README
      git:
        url: git@github.com:org/repo.git
        ref: c26b9b
      includePaths:
        - README.md

However, when I provide it such a config, I get the following.

Error: Parsing resource config 'vendir.yml': Unmarshaling config: Validating config:
Validating directory '.' (1): Expected path to not be one of '/', '.', '..', ''

I think the current assumption for the feature-set of the product is that vendir assumes control of everything in its CWD, so supporting something like this would cause it to stomp on existing files or something.

Anything else you would like to add:
[Additional information that will assist in solving the issue.]


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.

@caphrim007 caphrim007 added carvel-triage This issue has not yet been reviewed for validity enhancement This issue is a feature request labels Oct 7, 2021
@cppforlife cppforlife added carvel-accepted This issue should be considered for future work and that the triage process has been completed and removed carvel-triage This issue has not yet been reviewed for validity labels Oct 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Projects
Status: Unprioritized
Development

No branches or pull requests

2 participants