fix: update upload artifact to deployment script to use byte stream #2537
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
grace-rehn
requested review from
hnrkndrssn,
benPearce1,
IsaacCalligeros95 and
HuyPhanNguyen
benPearce1
approved these changes
Oct 18, 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.
The script to upload an artifact to an existing deployment prepends extra headers in the file content when uploading to Octopus.
This PR updates the script to use a byte stream instead of streaming as multipart form data. This ensures that the header content is not added to the artifact.
Fixes #2399
Tested using artifact.csv
Before
Running the original script and downloading the artifact from Octopus:
After
Running the new script and downloading the artifact from Octopus: