Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Developer tools give code-first developers control over how a Power Pages site moves from development to production. You keep the site in a Git repository that you manage, review changes through pull requests, and deploy with Azure Pipelines or GitHub workflows.
This article describes when to use developer tools and how they fit together. It follows ALM for developers in the Power Platform documentation. For the built-in alternative, see Use Git integration with Power Pages and Deploy Power Pages sites with pipelines in Power Platform.
When to use developer tools
- Standard data model sites: Developer tools are required. Standard data model configuration isn't solution-aware, so you can't promote it with Dataverse solutions, Git integration, or pipelines in Power Platform. Download the configuration as files, store them in source control, and upload them to each target environment.
- Enhanced data model sites and SPA code sites: Developer tools are optional. Consider them when you need code-first flexibility, when your organization already invests in Azure DevOps or GitHub, or when you need custom quality gates in your release process.
To check which data model a site uses, see Plan ALM for Power Pages.
How the toolchain fits together
A typical developer tools workflow looks like this:
- Download the site from a development environment with Power Platform CLI.
- Commit the files to a feature branch in your repository.
- Open a pull request, and merge the reviewed change into the main branch.
- Run CI/CD in Azure Pipelines or GitHub Actions to package the change as an artifact.
- Deploy the artifact to a test environment.
- Validate the site in test.
- After approval, deploy the same artifact to production.
Tools
Power Platform CLI
Power Platform CLI downloads and uploads Power Pages site content. For a walkthrough, see Tutorial: Use Microsoft Power Platform CLI with Power Pages.
| Command | Use it to |
|---|---|
pac pages download |
Download design studio site content. Use --modelVersion 1 for standard data model sites or --modelVersion 2 for enhanced data model sites. |
pac pages upload |
Upload design studio site content. Use --modelVersion to match the data model, and --deploymentProfile to apply environment-specific values during upload. |
pac pages download-code-site |
Download an SPA code site. |
pac pages upload-code-site |
Upload an SPA code site to a development environment. |
Use pac pages upload-code-site and pac pages download-code-site for SPA code sites. The pac pages upload and pac pages download commands are for design studio sites.
Microsoft Power Platform Build Tools
Microsoft Power Platform Build Tools add Power Platform tasks to Azure Pipelines. For Power Pages, use:
- Power Platform Download PAPortal and Power Platform Upload PAPortal to move design studio site content.
- Solution tasks, such as Power Platform Export Solution and Power Platform Import Solution, to move enhanced data model and SPA code sites as solutions.
For details, see Automate Power Pages deployments with Microsoft Power Platform Build Tools.
GitHub Actions for Microsoft Power Platform
GitHub Actions for Microsoft Power Platform add Power Platform actions to GitHub workflows. For Power Pages, use:
- The
upload-paportalportal task to upload design studio site content to a target environment. - Solution actions, such as
export-solutionandimport-solution, to move enhanced data model and SPA code sites as solutions.
For details, see Automate Power Pages deployments with GitHub Actions.
Combine developer tools with pipelines in Power Platform
Developer tools and built-in tools work together. Power Platform recommends that you use pipelines for core deployment and extend pipelines when you need to integrate with other CI/CD tools. For example, you can run a GitHub workflow as part of a pipeline. For details, see Extend pipelines using GitHub Actions.
Enhanced data model sites with developer tools
Enhanced data model sites are solution-aware, so you can promote them with solutions even when you use developer tools. Add the site and its dependencies to a solution as described in Use solutions with Power Pages, and then export and import the solution with Build Tools or GitHub Actions. Provide environment-specific values in a deployment settings file.
For SPA code sites, see CI/CD for single-page applications with developer tools.
Next steps
- Set up source control and branching for Power Pages
- Automate Power Pages deployments with Microsoft Power Platform Build Tools
- Automate Power Pages deployments with GitHub Actions