This repository was archived by the owner on Jan 5, 2026. It is now read-only.
Add workaround to temporarily use fixed version of Archive module #1870
Conversation
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
SteveL-MSFT
force-pushed
the
powershell-archive
branch
from
0a19005 to
0fb3cf8
Compare
SteveL-MSFT
force-pushed
the
powershell-archive
branch
from
0fb3cf8 to
d9ea853
Compare
cleemullins
approved these changes
May 3, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
The current Archive module that ships with PowerShell has an issue where it uses the backslash for directory path separator which creates archives that don't expand correctly on non-Windows machines as the backslash is a valid path character.
Until the PowerShell images (AzDevOps in this case for this build) gets updated to the (yet to be published) fixed version, this is a temporary workaround to pull down the latest version from master branch of Archive repo which has the fix.
Once the AzDevOps image is updated, this workaround should be removed.