architecture

作者: microsoft

架构图、层职责、关键文件、认证类型以及按症状分类的调试运行手册。

npx skills add https://github.com/microsoft/powerplatform-build-tools --skill architecture

Architecture & Debug Guide

Use this skill to understand the codebase architecture, trace issues across repos, or debug failures. If given a specific error or symptom, use the architecture map below to identify which layer is failing and follow the targeted debug steps for that layer.


Repo Dependency Map

powerplatform-build-tools  (THIS REPO — Azure DevOps Extension)
        │
        │  npm import (bundled)
        ▼
@microsoft/powerplatform-cli-wrapper  (TypeScript action library)
        │
        │  child_process.spawn()
        ▼
pac CLI binary  (pac.exe / pac — .NET, downloaded from NuGet at build time)
        │
        │  HTTPS REST
        ▼
Power Platform API  (Dataverse / crm.dynamics.com)

Layer Responsibilities

LayerOwnsDoes NOT own
build-toolsAzure DevOps task inputs, service connections, pipeline variables, artifact upload, task.jsonPower Platform logic, pac CLI args
cli-wrapperpac CLI argument assembly, auth flow, subprocess spawn/captureAzure DevOps APIs, pipeline variables
pac CLIPower Platform REST APIs, auth token management, all pac command semanticsNode.js, npm, Azure DevOps
Power Platform APIDataverse operations, solution lifecycleEverything above

Full Call Chain (export-solution as example)

Azure DevOps Pipeline
  │  task inputs: SolutionName, SolutionOutputFile, authenticationType, Environment
  ▼
src/tasks/export-solution/export-solution-v2/index.ts
  ├── TaskParser.getHostParameterEntries(taskDefinitionData)
  │     └── reads task.json → Record<string, HostParameterEntry>
  ├── getCredentials()
  │     ├── tl.getInput("authenticationType")  → "PowerPlatformSPN" | "PowerPlatformEnvironment"
  │     ├── tl.getEndpointAuthorization(endpointName)
  │     └── returns AuthCredentials { appId, clientSecret, tenantId, cloudInstance }
  ├── getEnvironmentUrl()
  │     └── checks (in order): task input → pipeline variable → env var → service connection URL
  │
  └── exportSolution(params, new BuildToolsRunnerParams(), new BuildToolsHost())
        │           ↑                    ↑
        │    runnersDir from          getInput() wraps
        │    POWERPLATFORMTOOLS_      tl.getInput()
        │    PACCLIPATH env var
        ▼
cli-wrapper: src/actions/exportSolution.ts
  ├── createPacRunner(runnerParams)   → CommandRunner (spawn wrapper)
  ├── authenticateEnvironment(pac, credentials, environmentUrl)
  │     └── pac("auth", "create", "--environment", url, "--applicationId", id,
  │               "--clientSecret", base64secret, "--tenant", tenantId, "--cloud", "Public")
  ├── InputValidator.pushInput(args, "--name", params.name)       → host.getInput(entry)
  ├── InputValidator.pushInput(args, "--path", params.path, resolveFolder)
  ├── InputValidator.pushInput(args, "--managed", params.managed)
  │   ... (assembles full arg list)
  │
  ├── pac("solution", "export", "--name", "MySolution", "--path", "/out/sol.zip", ...)
  │     ▼
  │   CommandRunner.ts: child_process.spawn("pac.exe", args, { env: { PP_TOOLS_AUTOMATION_AGENT: ... } })
  │     ├── stdout lines → logger.log()   → Azure DevOps build log
  │     ├── stderr lines → logger.error() → Azure DevOps build log
  │     └── exit 0 → resolve() | exit ≠ 0 → reject(RunnerError) → task fails
  │
  └── clearAuthentication(pac)
        └── pac("auth", "clear")

Key Files by Layer

build-tools (this repo)

FilePurpose
src/tasks/<name>/<name>-v2/index.tsTask entry point — reads inputs, calls cli-wrapper action
src/tasks/<name>/<name>-v2/task.jsonDeclares all task inputs, metadata, and execution config — execution handler is Node20_1 (primary) + Node16 (fallback)
src/host/BuildToolsHost.tsImplements IHostAbstractions — wraps tl.getInput(), artifact store
src/host/BuildToolsRunnerParams.tsImplements RunnerParameters — pac path, logger, agent string
src/host/CliLocator.tsFinds pac.exe/pac binary path by platform (win32 vs linux)
src/host/logger.tsImplements cli-wrapper's Logger interface — routes to tl.warning/error/debug and console.log
src/host/PipelineVariables.tsDefines output pipeline variable names (BuildTools.EnvironmentUrl, BuildTools.EnvironmentId, etc.) — used by create-environment and others
src/params/auth/getCredentials.tsExtracts auth from service connection — handles PowerPlatformEnvironment (UsernamePassword), PowerPlatformSPN (SPN or WIF, detected by authorization.scheme)
src/params/auth/getEnvironmentUrl.tsResolves target environment URL (4-level fallback chain)
src/parser/TaskParser.tsConverts task.json inputs array → Record<string, HostParameterEntry>
extension/extension-manifest.jsonAzure DevOps extension metadata
extension/task-metadata.jsonTask GUIDs per stage (LIVE / BETA / DEV / EXPERIMENTAL)
extension/service-connections.jsonPower Platform SPN endpoint definition
nuget.jsonpac CLI version pinned here — update to upgrade pac
webpack.config.jsFinds all task index.ts files, compiles each to dist/tasks/*/index.js
gulp/pack.mjsStages artifacts, injects task IDs per stage, runs tfx-cli to create VSIX

cli-wrapper (inside node_modules/@microsoft/powerplatform-cli-wrapper)

FilePurpose
dist/actions/exportSolution.tsAssembles pac args, calls pac, handles auth
dist/actions/importSolution.tsSame pattern for import
dist/actions/*.tsOne file per pac command
dist/pac/createPacRunner.tsResolves pac.exe path, returns CommandRunner
dist/pac/auth/authenticate.tsBuilds pac auth create / pac auth clear calls
dist/CommandRunner.tschild_process.spawn() wrapper — stdout/stderr capture, exit code handling
dist/host/InputValidator.tsPulls values through IHostAbstractions, normalizes, pushes to arg array

Authentication Types & Environment Variable Map

Auth TypeService Connection SchemeCredentials Passed to pac
Username/PasswordPowerPlatformEnvironment--username --password (base64)
Service PrincipalPowerPlatformSPN--applicationId --clientSecret (base64) --tenant
Workload Identity FederationPowerPlatformSPN + WIF scheme--applicationId --tenant --azureDevOpsFederated (via OIDC token env vars)

Note: Managed Identity is NOT supported through PPBT. getCredentials.ts only handles the three types above. WIF is detected when authorization.scheme === "WorkloadIdentityFederation" inside the PowerPlatformSPN branch — PPBT sets PAC_ADO_ID_TOKEN_REQUEST_URL / PAC_ADO_ID_TOKEN_REQUEST_TOKEN env vars and pac CLI handles the OIDC exchange.

Environment variables used by tasks:

VariableSet byUsed by
POWERPLATFORMTOOLS_PACCLIPATHtool-installer taskAll other tasks (to find pac.exe)
BuildTools.EnvironmentUrlcreate-environment taskAll other tasks (fallback env URL)
agent.diagnosticAzure DevOps agentAll tasks (enables --log-to-console on pac)
PP_TOOLS_AUTOMATION_AGENTCommandRunner.tspac CLI (user-agent telemetry)

Bundled Dependency Notes (affects vulnerability fixes)

These packages are in bundleDependencies — they ship inside the VSIX and their nested transitive deps are marked inBundle: true in package-lock.json. npm overrides cannot reach them. Lock file must be patched directly.

Bundled PackageKey nested depKnown issue
azure-pipelines-task-lib@5.2.8—No known issues (upgraded from 4.x which had minimatch@3.0.5 ReDoS)
@microsoft/powerplatform-cli-wrapper@0.1.135minimatch@10.x via glob@11Patched to 10.2.4 in lock file
fs-extra—No known issues
semver—No known issues

Debug Runbook by Symptom

npm install hangs indefinitely

Cause: npm re-resolves the full dependency tree when a new uncached package version is introduced. During re-resolution it hits npm.pkg.github.com for @microsoft/* packages.

  1. Check ~/.npmrc has a valid GitHub token: //npm.pkg.github.com/:_authToken=<token>
  2. Test auth: curl -s -o /dev/null -w "%{http_code}" -H "Authorization: token <token>" https://npm.pkg.github.com/@microsoft%2fpowerplatform-cli-wrapper → should return 200
  3. Run with verbose to find where it hangs: npm install --verbose 2>&1
  4. Check npm debug log: cat C:/.tools/.npm/_logs/<latest>-debug-0.log | tail -100
  5. If log shows 50,000+ placeDep ROOT minimatch lines → infinite loop from a conflicting flat minimatch override. Remove it.

npm install errors with registry auth

Cause: GitHub PAT expired or missing scopes.

  1. Token needs read:packages scope on github.com
  2. Token goes in ~/.npmrc as //npm.pkg.github.com/:_authToken=<token>
  3. The project .npmrc sets @microsoft:registry=https://npm.pkg.github.com/ and always-auth=true

Task fails: "pac.exe not found" or "POWERPLATFORMTOOLS_PACCLIPATH not set"

Cause: tool-installer task did not run before this task, or failed silently.

  • All tasks require tool-installer to run first — it sets POWERPLATFORMTOOLS_PACCLIPATH
  • Check CliLocator.ts for the exact path resolution logic
  • On Linux: pac binary needs execute permissions — CliLocator.ts sets them via chmod

Task fails: "auth create failed" or authentication errors

Layer: cli-wrapper authenticate.ts or pac CLI auth

  1. Check service connection credentials in Azure DevOps (Pipelines → Service Connections)
  2. Verify the auth type: SPN vs Username/Password vs Workload Identity
  3. Check cloudInstance — wrong cloud (e.g. sending to Public when env is UsGov) causes auth failure
  4. Check getCredentials.ts — resolveCloudInstance() maps the endpoint URL hostname to cloud name
  5. Enable diagnostics: set agent.diagnostic=true variable in pipeline → adds --log-to-console to pac

Task fails: "Solution not found" or pac CLI errors

Layer: pac CLI → Power Platform API

  1. Enable --log-to-console: set system.debug=true in pipeline variables
  2. Check the exact pac command being run in the build log (each arg is logged)
  3. The error is from pac.exe — check Power Platform documentation for that specific pac command
  4. Verify environment URL: getEnvironmentUrl.ts has a 4-level fallback — add explicit Environment input to the task to override

Build fails: TypeScript errors after upgrading packages

Layer: build-tools compile step

  1. npm run build → webpack + ts-loader
  2. TypeScript target is ES5, module is CommonJS (tsconfig.json)
  3. gulp-typescript is on ^6.0.0-alpha.1 — type errors may surface after TS version upgrades
  4. cli-wrapper interface changes break at compile time here — check IHostAbstractions and RunnerParameters

VSIX package has wrong task GUIDs / tasks conflict in marketplace

Layer: gulp/pack.mjs

  1. Task GUIDs per stage are in extension/task-metadata.json
  2. LIVE uses the canonical GUIDs; BETA/DEV/EXPERIMENTAL get unique GUIDs so they don't conflict
  3. pack.mjs substitutes GUIDs at pack time — verify the substitution logic if tasks show up under wrong IDs

Task fails: "Can't resolve AAD/OAuth authority"

Source: IcM recurring pattern (ADO #4863652) Layer: pac CLI auth → Power Platform API

  1. Usually caused by incorrect cloudInstance value — check getCredentials.ts → resolveCloudInstance()
  2. Verify the service connection URL matches the actual cloud (Public vs USGov vs China)
  3. Check if the tenant's AAD authority endpoint is reachable from the build agent (network/proxy issues)
  4. Enable diagnostics: set agent.diagnostic=true in pipeline variables for verbose pac auth logging

Task fails: WhoAmI error in non-English build agent context

Source: ADO #4846644 (long-term, no code fix yet) Cause: whoAmI.ts in cli-wrapper parses localized pac CLI output to extract the environment ID. Fails when the build agent OS locale is non-English. Workaround: Ensure build agent uses English locale (en-US). Set LANG=en_US.UTF-8 on Linux agents. Layer: cli-wrapper src/actions/whoAmI.ts ~line 40 — fix must go upstream to cli-wrapper repo.

Import solution fails with PVA (Power Virtual Agents) components

Source: IcM 604312672, ADO #4896777 Symptom: import-solution task fails when solution contains PVA components. Layer: pac CLI → Power Platform API (not a build-tools code issue) Workaround: Check pac CLI version — update nuget.json to latest pac CLI. If persists, raise with PAC CLI team.

Extension not working on Azure DevOps Server 2020 (on-prem)

Source: ADO #5130362 Official stance: Extension is not supported on Azure DevOps Server 2020 on-prem. Action: Deflect IcM tickets. Direct customers to Azure DevOps Services (cloud) or Server 2022+.

New pac CLI version needed

  1. Update version in nuget.json
  2. The pac version is also referenced in package.json for documentation — keep in sync
  3. Run gulp restore (or npm run prepare-pack) to download the new binary to bin/
  4. Test with bin/pac/pac.exe --version

Vulnerability in a bundled dependency

Cause: Packages in bundleDependencies have inBundle: true in lock file. npm audit fix and overrides cannot touch them. Fix procedure:

# 1. Get safe version metadata
npm view <package>@<safe-version> dist.tarball dist.integrity --json

# 2. Find the exact key in package-lock.json
#    (may be nested: node_modules/foo/node_modules/bar)
node -e "const l=require('./package-lock.json'); console.log(Object.keys(l.packages).filter(k=>k.includes('<package>')))"

# 3. Patch the lock file entry: update version, resolved URL, integrity hash

# 4. Apply
npm install
npm audit  # verify resolved

Task Pipeline Dependency Order

tool-installer          ← MUST run first (sets POWERPLATFORMTOOLS_PACCLIPATH)
      │
      ├── create-environment  → sets BuildTools.EnvironmentUrl pipeline variable
      │         │
      │         ├── import-solution
      │         ├── export-solution
      │         ├── pack-solution / unpack-solution
      │         ├── publish-customizations
      │         ├── set-solution-version
      │         └── deploy-package
      │
      ├── backup-environment → restore-environment
      ├── copy-environment
      └── delete-environment

Build Output Structure

npm run build
  └── webpack → dist/tasks/<task-name>/<task-name>-v2/index.js  (32 bundles)

npm run prepare-pack
  ├── webpack (above)
  └── gulp restore → bin/pac/pac.exe + bin/pac_linux/pac

npm run pack
  └── gulp pack
        ├── npm pack → out/npm-package/
        ├── stages to out/staging/ (dist/ + bin/ + extension/)
        ├── injects GUIDs from task-metadata.json (4 stages)
        └── tfx-cli → out/packages/
              ├── PowerPlatform-BuildTools-<ver>-LIVE.vsix
              ├── PowerPlatform-BuildTools-<ver>-BETA.vsix
              ├── PowerPlatform-BuildTools-<ver>-DEV.vsix
              └── PowerPlatform-BuildTools-<ver>-EXPERIMENTAL.vsix

来自 microsoft 的更多技能

oss-growth
microsoft
OSS增长黑客角色
agent-framework-azure-ai-py
microsoft
使用Microsoft Agent Framework Python SDK(agent-framework-azure-ai)构建Azure AI Foundry代理。在创建使用AzureAIAgentsProvider的持久化代理、使用托管工具(代码解释器、文件搜索、网络搜索)、集成MCP服务器、管理对话线程或实现流式响应时使用。涵盖函数工具、结构化输出和多工具代理。
development
airunway-aks-setup
microsoft
在AKS上设置AI Runway——从裸集群到运行模型。涵盖集群验证、控制器安装、GPU评估、提供商设置和首次部署。适用场景:“设置AI Runway”、“接入AKS集群”、“安装AI Runway”、“airunway设置”、“将模型部署到AKS”、“在AKS上进行GPU推理”、“在AKS上配置KAITO”、“在AKS上运行LLM”、“在AKS上使用vLLM”、“在AKS上设置模型服务”、“AI Runway控制器”。
devops
appinsights-instrumentation
microsoft
使用Azure Application Insights对Web应用进行插桩的指南。提供遥测模式、SDK设置和配置参考。适用场景:如何对应用进行插桩、App Insights SDK、遥测模式、什么是App Insights、Application Insights指南、插桩示例、APM最佳实践。
devops
applicationinsights-web-ts
microsoft
使用Application Insights JavaScript SDK(@microsoft/applicationinsights-web)为浏览器/Web应用添加检测。用于真实用户监控(RUM)——页面视图、点击、AJAX/fetch依赖项、异常、自定义事件,以及与后端OpenTelemetry追踪关联的浏览器端GenAI代理追踪。涵盖SDK加载器脚本和npm设置、框架扩展(React、React Native、Angular)、点击分析、遥测初始化器,以及从浏览器发出的代理/工具/模型跨度所遵循的OTel GenAI语义约定。
devops
azure-ai-anomalydetector-java
microsoft
使用适用于 Java 的 Azure AI 异常检测器 SDK 构建异常检测应用程序。在实现单变量/多变量异常检测、时间序列分析或 AI 驱动的监控时使用。
development
azure-ai-language-conversations-py
microsoft
使用azure-ai-language-conversations Python SDK实现对话语言理解(CLU)。当使用ConversationAnalysisClient分析对话意图和实体、构建NLP功能或将语言理解集成到应用程序中时使用。
development
azure-ai-ml-py
microsoft
Azure Machine Learning SDK v2 for Python。用于机器学习工作区、作业、模型、数据集、计算资源和管道。 触发词:“azure-ai-ml”、“MLClient”、“工作区”、“模型注册表”、“训练作业”、“数据集”。
development