[rush] New parameters for Azure Storage plugin #4995
Merged
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
dmichon-msft
requested review from
iclanton,
octogonz,
apostolisms and
D4N14L
as code owners
dmichon-msft
force-pushed
the
azure-default-credential
branch
from
64bc0ed to
cccbf83
Compare
D4N14L
reviewed
Nov 8, 2024
...gins/rush-azure-storage-build-cache-plugin/src/schemas/azure-blob-storage-config.schema.json
Outdated
Show resolved
Hide resolved
D4N14L
approved these changes
Nov 8, 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.
Summary
Improve configurability of
rush-azure-storage-build-cache-plugin.Details
Adds new configuration properties:
loginFlowallows specifying the interactive login flow to use: one ofAdoCodespacesAuth,InteractiveBrowserorDeviceCode. Defaults toInteractiveBrowser(will fall back toDeviceCode).readRequiresAuthenticationwill make not having a valid SAS token a fatal error during cache read.How it was tested
PR release