Github actions9/17/2023 If you don't specify a target branch, then your solution is committed to the Source Branch.Google Cloud customers depend on Google Cloud Deploy to deliver their software to production. - Replace with the Git branch to create for the solution commit.- Replace with the Git branch to commit the solution.- Replace with your GitHub workflow YAML file name.- Replace with your GitHub repository name.- Replace with your GitHub organization name.- Replace with your GitHub personal access token.The PAT is passed in the Authorization header of the HTTP request. For more information on how to create a GitHub personal access token see Creating a personal access token. artifact_url: solution_name: user_name: commit_message: flow also uses a personal access token (PAT) to authenticate with GitHub.The commit_message is pulled from the deployment stage run row in Dataverse. The values passed into the artifact_url, solution_name, and user_name are pulled from the outputs of the action that triggered the pipeline. commit_message: Message to provide for the commit.target_branch: Branch to create for the solution commit.source_branch: Source branch for the solution commit.solution_name: Name of the solution in the Dataverse environment.artifact_url: URL of the Dataverse solution artifact created by the pipelines.Include the following inputs in the request body: The flow passes the required inputs to the GitHub workflow. The flow calls the HTTP connector to trigger the GitHub workflow. The flow triggers when the OnDeploymentRequested action is run in Dataverse. For more information on how to create a Power Automate flow, see Create a flow. The flow can be configured to pass the required inputs to the GitHub workflow. To call a GitHub workflow, you can create a Power Automate flow that is triggered when a deployment request is made in Dataverse. name: Download, unpack and commit the solution to git Listed below is the GitHub Actions workflow code. CLIENT_SECRET: The client secret of the registered Azure AD application.įor more information see Creating and using encrypted secrets and Create an application user.TENANT_ID: The tenant ID of the Azure AD directory associated with the Azure AD application.CLIENT_ID: The client ID of the registered Azure AD application.Configure these secrets in the GitHub repository settings. The following secrets are required to connect to Dataverse using an Application User configured in Dataverse and in Azure Active Directory (AD). commit_message (required): Message to provide for the commit.If not specified, the source_branch is used. target_branch (optional): Branch to create for the solution commit.source_branch (required): Branch for the solution commit.solution_name (required): Name of the solution in the Dataverse environment.artifact_url (required): The URL of the Dataverse row (record) ID for the artifact created by the pipelines.The following workflow inputs are required or optional: push to branch: Pushes the committed changes to the source branch.commit changes: Commits changes to the existing or new branch.download solution from artifact: Downloads the solution from the artifact created by pipelines.create new branch if specified: Creates a new branch if a target_branch is specified in the inputs.The workflow consists of the following steps: The workflow runs on ubuntu-latest and has the contents: write permission to be able to commit changes to the GitHub repository branch. The workflow is triggered via a workflow_dispatch event. When a pipelines deployment is submitted, a cloud flow triggers the GitHub workflow to download, unpack, and commit the artifact's source code to a GitHub branch. This article demonstrates using GitHub Actions and Power Automate cloud flows for extending pipelines in Power Platform.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |