Skip to content

Migrating Managed Identities to WIF Service Connections #8292

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Stella Huang (StellaHuang95) merged 2 commits into from
Sep 22, 2025
Merged

Migrating Managed Identities to WIF Service Connections #8292

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
6b30f49
managed identity
StellaHuang95 Sep 22, 2025
768024b
bootstarpper
StellaHuang95 Sep 22, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions Build/templates/create_vs_bootstrapper.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,7 @@ steps:
- task: MicroBuildBuildVSBootstrapper@3
displayName: 'Build Bootstrapper'
inputs:
azureSubscription: 'VSEng-VSDrop-MI' # SERVICE CONNECTION
channelName: 'IntPreview'
vsMajorVersion: '18'
bootstrapperCoreFeedSource: 'https://devdiv.pkgs.visualstudio.com/_packaging/Setup/nuget/v3/index.json'
Expand All @@ -14,6 +15,8 @@ steps:
# this outputFolder must match the "dropFolder" in the 1ES.MicroBuildVstsDrop@1 task in azure-pipelines.yml
outputFolder: $(Build.StagingDirectory)\release
manifests: $(Build.StagingDirectory)\release\Microsoft.PythonTools.vsman
env:
SYSTEM_ACCESSTOKEN: $(System.AccessToken) # Add the system access token.

# Publish the bootstrapper as a build artifact.
# We do this manually instead of using the templateContext outputs because we don't need sbom generation.
Expand Down
8 changes: 5 additions & 3 deletions Build/templates/publish_symbols.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,10 +27,12 @@ steps:
# When you insert your binaries into VS or ship them to any other client you need to archive your binaries & symbols to MSDL.
# This will ensure that your symbols are available even if the associated build is deleted and will also make them available
# on the internet so that external clients can download them.
- task: MicroBuildArchiveSymbols@5
- task: MicroBuildArchiveSymbols@6
displayName: 'Archive Symbols'
inputs:
SymbolsFeatureName: PTVS
SymbolsProject: VS
azureSubscription: Symbols Upload (DevDiv)
SymbolsAgentPath: '$(Build.ArtifactStagingDirectory)/symbols'
azureSubscription: 'VSEng-SymbolsUpload' # SERVICE CONNECTION
SymbolsAgentPath: '$(Build.ArtifactStagingDirectory)/symbols'
env:
SYSTEM_ACCESSTOKEN: $(System.AccessToken) # Add the system access token.
2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,6 @@
"name": "ptvs",
"private": true,
"devDependencies": {
"@pylance/pylance": "2025.8.1"
"@pylance/pylance": "2025.8.2"
}
}