[Storage] When download blob with parameter AbsoluteUri, not allow input parameter Context #26585
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
| Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status. |
…Uri (alias Uri, BlobUri), not allow input parameter Context together.
VeryEarly
pushed a commit
to VeryEarly/azure-powershell
that referenced
this pull request
Nov 5, 2024
…put parameter Context (Azure#26585) * [Storage] fix Azure#26316: When download blob with parameter AbsoluteUri (alias Uri, BlobUri), not allow input parameter Context together. * Add static exception * revise change log
6 tasks
vidai-msft
added a commit
that referenced
this pull request
Nov 7, 2024
#26599) * [Storage] When download blob with parameter AbsoluteUri, not allow input parameter Context (#26585) * [Storage] fix #26316: When download blob with parameter AbsoluteUri (alias Uri, BlobUri), not allow input parameter Context together. * Add static exception * revise change log * resolve merge --------- Co-authored-by: Wei Wei <[email protected]> Co-authored-by: Vincent Dai <[email protected]>
github-actions bot
pushed a commit
that referenced
this pull request
Nov 7, 2024
#26599) * [Storage] When download blob with parameter AbsoluteUri, not allow input parameter Context (#26585) * [Storage] fix #26316: When download blob with parameter AbsoluteUri (alias Uri, BlobUri), not allow input parameter Context together. * Add static exception * revise change log * resolve merge --------- Co-authored-by: Wei Wei <[email protected]> Co-authored-by: Vincent Dai <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
The breaking change warning is already added, and remove with this PR.
Add the change since the -Context parameter is actually not used when download blob with Uri. So remove it to avoid confusing like issue #26316.
Mandatory Checklist
Please choose the target release of Azure PowerShell. (⚠️ Target release is a different concept from API readiness. Please click below links for details.)
Check this box to confirm: I have read the Submitting Changes section of
CONTRIBUTING.mdand reviewed the following information:ChangeLog.mdfile(s) appropriatelysrc/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.## Upcoming Releaseheader in the past tense.ChangeLog.mdif no new release is required, such as fixing test case only.