Deployment approval and scheduling using Power Platform Pipelines! In this video, I am showing you how to build automations around Power Platform Pipelines deployments, for example, to request for approval before the actual deployment is made. Also, how to get and store managed and unmanaged solution files, so that you can create a version history in a file repository of your choice. And in case you didn't notice, you are now able to schedule the deployment as well.
Documentation for extending Power Platform Pipelines: learn.microsoft.com/en-us/power-platform/alm/extend-pipelines
The document outlines the extensibility of Application Lifecycle Management (ALM) processes using pipelines in Microsoft Dataverse, emphasizing the benefits of integration with various other systems. Options for customization vary, including no-code, low-code, and pro-code, and may integrate with CI/CD applications like Azure DevOps, GitHub, etc. Pipelines raise various business events that trigger custom logic and can be connected to multiple platforms, such as Power Automate, Azure Service Bus, Azure Event Hubs, Webhooks, and Dataverse plug-ins.
The capability to extend pipelines is gradually being introduced. A key feature is the addition of predeployment conditions, allowing the configuration of a gate for each pipeline stage. Once a deployment is submitted, the request remains pending until business logic is executed and signals the pipeline host to complete or reject the deployment. It's important to note that the system prevents tampering or modification of the exported solution artifact.
The document also details triggers at each pipeline deployment step, offering real-time events at the beginning and completion of the step. These triggers are available in Power Automate cloud flows. Furthermore, Power Automate trigger conditions allow customization so that the flow only runs when certain conditions are met.
The system allows users to set conditions for specific pipelines, stages, or a combination of both. The document also covers the actions to take after running the desired predeployment logic in cloud flows, which includes updating the PreDeploymentStepStatus.
Moreover, the document presents detailed information about event details, input parameters, output parameters, and their specific comments for each step of the pipeline deployment process. Lastly, the document provides a link to download a sample solution for understanding the triggers and actions with pipelines, and guides on how to run pipelines in Power Platform.
Power Platform Pipelines is a powerful tool that allows you to automate deployment processes, create version histories, and schedule deployments with ease. You can easily extend its capabilities by following the provided documentation, and incorporate it into your existing development environment to streamline your workflows. Stay up-to-date with the latest updates and limitations to make the most out of Power Platform Pipelines in your projects.
In this video, you will learn how to build automations for Power Platform Pipelines deployments, such as how to request for an approval before the actual deployment. You will also learn how to get and store managed and unmanaged solution files, so that you can create a version history in a file repository. You will also learn how to schedule the deployment. Additionally, you will learn about the limitations of Power Platform Pipelines. Finally, you will learn how to extend Power Platform Pipelines.
Power Platform Pipelines, Automations, Approval Requests, Managed Solutions, Unmanaged Solutions, Deployment Scheduling, Version History, Power Platform Limitations, Power Platform Documentation, Extending Power Platform Pipelines