$ loading_
为 Power Pages 站点配置环境变量与部署设置，支持多环境 ALM 发布。
复制安装指令，让 AI 自动完成配置 · 推荐新手
请帮我安装 askskill 上的 "configure-env-variables" 技能： 1. 下载 https://raw.githubusercontent.com/microsoft/power-platform-skills/main/plugins/power-pages/skills/configure-env-variables/SKILL.md 2. 保存为 ~/.claude/skills/configure-env-variables/SKILL.md 3. 装好后重载技能，告诉我可以用了
请为我的 Power Pages 站点配置环境变量，用于区分开发、测试和生产环境的站点设置，并生成 deployment-settings.json。
创建环境变量定义，说明如何在 Power Pages Management 中绑定站点设置，将变量加入解决方案，并生成包含各环境覆盖值的 deployment-settings.json。
帮我把现有 Power Pages 站点设置改造成环境相关配置，避免不同环境共用同一组固定值。
识别适合参数化的站点设置，创建对应环境变量，提供逐步绑定指引，并整理部署时所需的环境覆盖配置。
请为这个 Power Pages 解决方案补齐部署变量配置，把相关环境变量加入解决方案，并输出可用于发布流程的 deployment-settings.json。
输出适合 ALM 的变量配置方案，包括 Dataverse 环境变量定义、解决方案纳入清单、站点设置映射说明及发布配置文件。
Plugin check: Run
node "${CLAUDE_PLUGIN_ROOT}/scripts/check-version.js"— if it outputs a message, show it to the user before proceeding.
Creates and links Dataverse environment variables to Power Pages site settings, enabling different configuration values per deployment environment (dev vs staging vs prod). Generates deployment-settings.json for use by deploy-pipeline.
Power Pages site settings can be backed by environment variables (GA March 2025, enhanced data model only). When linked:
mspp_source changes from 0 (static) to 1 (environment variable)mspp_valuedeploymentsettingsjsonAPI note: The site setting → env var link is set via a HAR-confirmed OData PATCH pattern (v9.0, EnvironmentValue nav property, if-match: * and headers required). This is handled by . All steps are fully automated.
clienthost: Browserscripts/lib/link-site-setting-to-env-var.jspac auth whoaz account get-access-token.solution-manifest.json exists in the project root (run setup-solution first).powerpages-site/ folder exists)
plan-almis the front door. When the user expresses an ALM intent (promote / ship / deploy / set up CI-CD / move to staging / push to prod), the orchestrator (/power-pages:plan-alm) should run first. This Phase 0 enforces that and is meant to fail closed when there's no plan, not to be a one-time check the user can dismiss forever.
Skip rule. If this skill was invoked as part of an active plan-alm orchestration, skip Phase 0 entirely and proceed to Phase 1. The gate helper exposes this via its inExecution block — pass through silently to Phase 1 when:
inExecution.status === "active"
The helper computes this from docs/.alm-plan-data.json — PLAN_STATUS === "In Execution" AND LAST_INVOCATION_AT within the last 60 minutes. check-alm-plan.js refreshes LAST_INVOCATION_AT automatically on every invocation that finds the plan in execution, so each in-chain skill keeps the chain alive for the next one — even multi-hour deploys (deploy-pipeline alone can take 60 min per stage) survive the window without the chain incorrectly de-classifying. Stalled chains (no heartbeat for > 60 min) reclassify as stale-heartbeat and Phase 0 gates fire normally so an abandoned plan doesn't silently bypass user confirmation.
When inExecution.status is anything other than "active" ("not-running", "stale-heartbeat", "no-plan"), run the Phase 0 gate flow below. Branch on the remaining helper fields:
Step 1 — Run the gate helper.
node "${CLAUDE_PLUGIN_ROOT}/scripts/lib/check-alm-plan.js" --projectRoot "."
The helper returns JSON with { exists, deferred, stale, staleness: { reason, detail }, generatedAt, planStatus, ... }. Pass --envUrl, --token, --solutionId once Phase 1 has acquired them if you also want a freshness check; otherwise the helper does an existence-only check, which is sufficient for the gate decision below.
Step 2 — Branch on the result.
| Result | Behavior |
|---|---|
deferred: true | The user has explicitly deferred ALM for this project (.alm-deferred marker present). Pass through silently to Phase 1 — do not nag. |
exists: false | The user hasn't run plan-alm yet. See Step 3. |
exists: true, stale: false | Plan is current. Pass through silently to Phase 1. |
exists: true, stale: true (reason: solution-modified) | The solution changed after the plan was generated. See Step 4. |
Step 3 — No plan. Tell the user:
…
为 Power Apps 代码应用接入 Azure DevOps 连接器，便于查询工单、提报缺陷与管理流水线。
将现有 Power Pages 代码站点构建并部署到目标环境，完成认证与上传流程。