Document how to use Workflow Identity Federation #426
+187
−0
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
Resolves https://devdiv.visualstudio.com/DevDiv/_workitems/edit/2046511/ I am unable to actually try this end to end myself as recent policy enforcement on the vcpkg team's Azure Subscription renders some of the actions a user needs to do here impossible. However, I did verify that the SAS token generation bits do reasonable things with my SC-ALT account.
|
@BillyONeal : Thanks for your contribution! The author(s) have been notified to review your proposed change. @bion |
|
Learn Build status updates of commit 6ae487d: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
PRMerger Results
|
JavierMatosD
approved these changes
Nov 12, 2024
Comment on lines
108
to
115
| In the yml where you wish to invoke vcpkg in Azure DevOps, use the AzureCLI@2 task to mint a SAS | ||
| token and invoke vcpkg, for example: | ||
|
|
||
| ::: zone pivot="shell-cmd" | ||
|
|
||
| Generating the end date with cmd is impractical; please choose powershell or bash. | ||
|
|
||
| ::: zone-end |
There was a problem hiding this comment.
Suggested change
| In the yml where you wish to invoke vcpkg in Azure DevOps, use the AzureCLI@2 task to mint a SAS | |
| token and invoke vcpkg, for example: | |
| ::: zone pivot="shell-cmd" | |
| Generating the end date with cmd is impractical; please choose powershell or bash. | |
| ::: zone-end | |
| ::: zone pivot="shell-cmd" | |
| >[!NOTE] | |
| >Generating the end date with cmd is impractical. Please choose PowerShell or Bash. | |
| ::: zone-end |
There was a problem hiding this comment.
Also, maybe we should explain what we mean by choosing PowerShell of Bash.
Comment on lines
117
to
119
| ::: zone pivot="shell-powershell" | ||
|
|
||
| ```yaml |
There was a problem hiding this comment.
Suggested change
| ::: zone pivot="shell-powershell" | |
| ```yaml | |
| ::: zone pivot="shell-powershell" | |
| In the yml where you wish to invoke vcpkg in Azure DevOps, use the AzureCLI@2 task to mint a SAS | |
| token and invoke vcpkg, for example: | |
| ```yaml | |
Ditto below. I think that will look cleaner if the user has cmd selected.
|
Learn Build status updates of commit 733cd61:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| vcpkg/consume/caching-workflow-identity-federation.md | View | Details | |
| vcpkg/TOC.yml | ✅Succeeded | View |
vcpkg/consume/caching-workflow-identity-federation.md
- Line 17, Column 1: [Warning: h1-not-first - See documentation]
Markdown content is not allowed before H1 'Tutorial: Set up caching using Azure Storage and Azure DevOps'.
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:
- Try searching the learn.microsoft.com contributor guides
- Post your question in the Learn support channel
|
Learn Build status updates of commit aa6660f: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
PRMerger Results
|
Thomas1664
reviewed
Nov 14, 2024
| > [!WARNING] | ||
| > These instructions grant permission to act as the managed identity to the pipelines where it is | ||
| > used. Moreover, vcpkg caches provide a mechanism where a compromised build may be able cause |
There was a problem hiding this comment.
Suggested change
| > used. Moreover, vcpkg caches provide a mechanism where a compromised build may be able cause | |
| > used. Moreover, vcpkg caches provide a mechanism where a compromised build may be able to cause | |
| named `vcpkg-docs-identity-connection`. At this point, Azure DevOps should be showing an issuer | ||
| and subject identifier. | ||
|
|
||
| In another tab, to the Azure Portal navigate to the managed identity created in step 1. On the left |
There was a problem hiding this comment.
I think there's something wrong with this sentence, but I'm not entirely sure what was intended here.
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.
Resolves https://devdiv.visualstudio.com/DevDiv/_workitems/edit/2046511/
I am unable to actually try this end to end myself as recent policy enforcement on the vcpkg team's Azure Subscription renders some of the actions a user needs to do here impossible. However, I did verify that the SAS token generation bits do reasonable things with my SC-ALT account.