-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* Add file.symlink.create capability and wire it up * Run codegen for new FileActionSymlink Message * Add Symlink test * Add user/group ownership and timestamps to symlink ** Symlinks have user/group ownership that are independent of those of the target file; in linux, the ownership of the symlink itself is only checked when the link resides in a directory with the sticky bit set and the link is the subject of removal or renaming. The sticky bit prevents files in the directory from being deleted or renamed by non-owners (members of the group that owns the file may not delete the file; the user must own the file). In addition to user/group restrictions, linux symlinks have timestamps that are independent of the timestamps on the target file. * Expose symlink options to `llb` package * Add symlink integration test * Use tar exporter for tests ** Using the local exporter causes the files to be exported with the permissions of the user who does the exporting, instead of retaining their file permissions from within the container. Using the tar exporter instead preserves the permissions until they can be checked. * Change symlink fields to `oldpath` and `newpath` ** Also run `make generated-files` * Fix typo * Add doc strings to exported `llb` identifiers * Remove `requiresLinux` from integration test * Revert "Remove `requiresLinux` from integration test" Signed-off-by: Peter Engelbert <[email protected]>
- Loading branch information
1 parent
c3baf4c
commit ac50320
Showing
13 changed files
with
1,006 additions
and
194 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.