public_git
/
kaniko
mirror of https://github.com/GoogleContainerTools/kaniko
1
0
Fork 0
Code Issues Releases Wiki Activity

update about filesWithParentDirs

This commit is contained in:
cvgw 2020-02-17 13:32:28 -08:00
parent 84047d4bcd
commit d31d2bc74c
1 changed files with 8 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
docs/design_proposals/filesystem-resolution-proposal-01.md
View File

@ -87,6 +87,11 @@ The API will iterate over the set of filepaths and for each item
* check whether the target is whitelisted and if * check whether the target is whitelisted and if
not add the target to the output not add the target to the output
All ancestors of each filepath will also be added to the list, but the previous
checks will not be applied to the ancestors. This maintains the current behavior
which we believe is needed to maintain correct permissions on the ancestor
directories.
### Open Issues/Questions ### Open Issues/Questions
\<Ignore symlinks targeting whitelisted paths?\> \<Ignore symlinks targeting whitelisted paths?\>
@ -109,7 +114,9 @@ current whitelist logic it is possible for `/some/dir` to be whitelisted but not
ancestors does it make most sense to handle this within the proposed filtering ancestors does it make most sense to handle this within the proposed filtering
API? API?
Resolution: Not Yet Resolved Resolution: Resolved
Yes, this should be handled in the API
\<Should the API handle diff'ing files?\> \<Should the API handle diff'ing files?\>