-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Sync: subtree sync needs documentation #1837
Comments
well - the best place would be https://skaffold.dev/docs/how-tos/filesync/ but it's lacking a bit of documentation still :) |
Also, I'm not fully convinced about triple star just yet...it's so non-standard...not that globs have any kind of standard (especially with docker's lack of ability to do preserved subtrees moby/moby#15858), but I feel like we are adding to the confusion with triple star. |
Should be put on hold until #1844 is settled. |
@balopat dont' worry @corneliusweig is taking that in to consideration in the design proposal something we can discuss later. |
Sorry, closed by accident |
Is there a way to sync subtrees with v0.25.0 ? |
@pulse14 Yes,
This will sync all py-files below |
@corneliusweig That syntax does not work for me in v0.25.0, the files are all copied to the root of the dest folder without the folder structure preserved. Is there a separate issue open for this? |
I agree. I have |
@pulse14 @corneliusweig Nevermind, I see that the pull request to add |
@747823 🤦♂️ you are right, sorry for that confusion! |
I'm really curious about what the use case is for the current way ** works? I just don't see when you would want to flatten out a directory like that. |
Ignore best practices for npm and work without package-lock.json. This file is ~300kb and should not bloat the skaffold repository. Signed-off-by: Cornelius Weig <22861411+corneliusweig@users.noreply.github.com>
Superseded by #1994 |
Information
PR #1813 introduced the triple-star syntax for the sync map:
Its purpose is to recreate the directory structure under foo at the destination (see also #1807).
This feature needs some documentation. But where should it be documented?
EDIT The syntax may be changed. See #1844 and #1847.
The text was updated successfully, but these errors were encountered: