You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While building out a Docker Compose-style plugin and validating it against our own real development stack, we ran into two classes of problems in the build-context path, and to fix them we had to make changes to the container app, but part of the changes were archive-authoring concerns and belong in ContainerizationArchive, not in higher-level callers. The result is a reusable API for explicit archive creation and more portable archives when symlinks point to other archived content.
This PR adds a generic explicit-entry archive API to ContainerizationArchive and improves symlink handling so archives remain relocatable after extraction.
In addition to archiveDirectory(_:), callers can now provide an ordered list of source entries to archive. This makes it possible to archive a precomputed file set without rewalking the source tree and centralizes symlink handling in the archive layer itself.
Testing
add regression coverage for explicit-entry archive creation
add round-trip tests for:
internal absolute symlinks rewritten to archive-relative paths
external absolute symlinks preserved unchanged
canonicalized internal absolute symlinks through symlinked ancestors
verify existing archive-directory symlink behavior still passes
Passed:
swift test --filter archiveEntries
swift test --filter archiveDirectoryRewritesInternalAbsoluteSymlink
swift test --filter archiveDirectorySymlinkInside
swift test --filter archiveDirectorySymlinkOutsideExcluded
This file contains hidden or 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
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Context and Motivation
While building out a Docker Compose-style plugin and validating it against our own real development stack, we ran into two classes of problems in the build-context path, and to fix them we had to make changes to the
containerapp, but part of the changes were archive-authoring concerns and belong inContainerizationArchive, not in higher-level callers. The result is a reusable API for explicit archive creation and more portable archives when symlinks point to other archived content.(Related
containerPR: apple/container#1391)This PR adds a generic explicit-entry archive API to
ContainerizationArchiveand improves symlink handling so archives remain relocatable after extraction.In addition to
archiveDirectory(_:), callers can now provide an ordered list of source entries to archive. This makes it possible to archive a precomputed file set without rewalking the source tree and centralizes symlink handling in the archive layer itself.Testing
Passed: