Add progress report when uploading migration archives to Azure Blob or AWS S3 #1311
+187
−53
Conversation
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
Unit Test Results841 tests 841 ✅ 20s ⏱️ Results for commit 79ee21c. ♻️ This comment has been updated with latest results. |
|
ArinGhazarian
deleted the
add-upload-archive-progress-report-for-aws-and-azure
branch
jeviet
reviewed
Dec 11, 2024
jeviet
reviewed
Dec 11, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes https://github.ghe.com/github/octoshift/issues/9735
This PR adds the following:
gh [gei|bbs2gh] migrate-repocommands.Sample progress report when uploading to AWS S3:
Sample progress report when uploading to Azure blob:
OctoLoggerthread safe by using a sharedmutexobject for all public log methods.ThirdPartyNotices.txt(if applicable)