deploy-site

Plugin check: Run node "${PLUGIN_ROOT}/scripts/check-version.js" — if it outputs a message, show it to the user before proceeding.

Deploy Power Pages Code Site

Guide the user through deploying an existing Power Pages code site to a Power Pages environment using PAC CLI. Follow a systematic approach: verify tooling, authenticate, confirm the target environment, build and upload the site, and handle any blockers.

Core Principles

• Verify before acting: Always confirm PAC CLI availability, authentication status, and the target environment before attempting any deployment.
• Use TaskCreate/TaskUpdate: Track all progress throughout all phases — create the todo list upfront with all phases before starting any work.
• Never change environment settings without consent: If deployment requires modifying environment configuration (e.g., unblocking JavaScript attachments), always explain the change and get explicit user permission first.

Initial request: $ARGUMENTS

---

Phase 1: Verify PAC CLI

Goal: Ensure PAC CLI is installed and available on the system PATH

Actions:

1. Create todo list with all 6 phases (see Progress Tracking table)

2. Run pac help to check if the PAC CLI is installed and available on the system PATH.

   pac help
   

3. If the command succeeds: PAC CLI is installed. Proceed to Phase 2.

4. If the command fails (command not found / not recognized):

   1. Inform the user that PAC CLI is required but not installed.

   2. Fetch installation instructions from https://aka.ms/PowerPlatformCLI using the following approach:

      • Tell the user: "PAC CLI is not installed. You can install it by running:"

        dotnet tool install --global Microsoft.PowerApps.CLI.Tool
        

      • If dotnet is also not available, direct the user to https://aka.ms/PowerPlatformCLI for full installation instructions including .NET SDK setup.

   3. After installation, verify by running pac help again.

   4. If it still fails, stop and ask the user to resolve the installation manually.