Correctly handle public Azure Blob Storage containers containing one file #54
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.
This PR (1) correctly handles single-file public containers for Azure Blob Storage and (2) updates input file line counting logic to correctly handle empty lines at the end of the file (permutations.txt).
For (1), the current script will print
Empty Public Container Available:
for a public Azure Blob Storage container with a single file. The fix wraps the XML response in an array to ensure that$foundUrl
is a single-elementObject[]
rather than a singleXmlElement
(whose.Length
property would be$null
) when there is only one file in the container.For (2), calls to
Write-Progress
will error when there are empty lines anywhere in $Permutations or $Folders as the words iterator will exceed the line count calculation. This results in a value >100 getting passed to the -PercentComplete parameter.