Hi there! 👋 I noticed in the README that these actions are listed as pre-release. Do you know of a rough timeline to GA / v1? 🙏

I am using this GA https://github.com/microsoft/powerplatform-actions-lab/blob/main/sample-workflows/release-solution-to-prod.yml
and the import fails with this error message

Starting Solution Import: 1/7, 14%.

Import of solution file completed: 2/7, 28%.
Waiting on completion of import job 'dc273664-d71b-4dda-8434-8a8f272f1dbf': 3/7, 42%.

Processing of import job ended at 11/20/2020 7:25 AM after 100% completion: 4/7, 57%.
Import job reported a status of 'SUCCESS': 5/7, 71%.

Unmanaged solution import has completed, starting to publish customizations: 6/7, 85%.

Sorry, the app encountered a not recoverable error and will need to terminate. The exception details have been captured and will be forwarded to the development team, if telemetry has been enabled. Exception Id:2006bae8-a20c-45d7-b21c-806f98f5ee8c

When I log in to the power apps website I can see the solution was imported and I can publish it manually.

reported by @navin22

Folks, to keep things together with regard to the issues the folks have been having with the PowerPlatform Actions, and compensations we may need to ask of you, we are going to update this thread going forward and link the other issues to it.

#174
#173
#172

At this time, we have tracked the issue back to a GitHub Runner update that updated the way actions were checked out.
This change seems to have impacted actions that rely on the large file system support for gitHub as part of managing assets for actions.

We are working directly with the github Runner's team actively to resolve this issue.

We are concurrently working to develop a workaround to the root issue and will post here once we have determined the best way to unblock your workflows.

Hi
I am trying to create a new environment which includes a template.
Despite populating the "Templates" parameter, the result is a standard blank Dataverse environment.

I used the code below

  name: create-environment action
  uses: microsoft/powerplatform-actions/[email protected]
  id: create_environment
  with:
    user-name: ${{ github.event.inputs.admin_username }}
    password-secret: ${{ github.event.inputs.admin_password }}
    name: ${{ github.event.inputs.env_name }}
    region: ${{ github.event.inputs.env_region }}
    type: SubscriptionBasedTrial
    currency: ${{ github.event.inputs.env_currency }}
    language: ${{ github.event.inputs.env_language }}
    domain: ${{ github.event.inputs.env_domain }}
    templates: ${{ github.event.inputs.env_templates }}

This is the resulting output

Is it possible to specify a template? Am I missing something? The same parameter works on Power Shell Cmdlets.
Thank you!

Help me please with the timeout in the import-solution step.
When it lasts more than 2 minutes, I have an error.
How can I increase the time-out value for this step?

Hi,
I would like to make a request about vulnerabilities detect in the security scan.
I have clone this repository and I have passed a security scan. The Dependabot alerts show vulnerabilities related to dependencies version included in the package-lock.json:

ansi-regex version 5.0.0 --> fixed vulnerability in version 5.0.1 or later
postcss version 7.0.36-->fixed vulnerability in version 8.2.13 or later
node-fetch version 2.6.1--> fixed vulnerability in version 2.6.7 or later
nanoid version 3.1.20--> fixed vulnerability in version 3.1.31 or later
glob-parent version 3.1.0 --> fixed vulnerability in version 5.1.2 or later

Please, I would like to know if there is any plan to upgrade these dependencies version in orden to fix the vulnerabilities.

Thanks in advanced

The newer versions of pac have a --settings-file option for working with the new deployment settings files. It would be great to have access to this in the import solution action.

I am using microsoft/powerplatform-actions/branch-solution@v0 .When it try to push to existing branch it fails.
! [rejected] preqa -> preqa (non-fast-forward)

We have the following action defined in a GitHub workflow:

jobs:
  package-and-release:
    name: Package and Release
    runs-on: windows-latest
    steps:
      - uses: actions/checkout@v3
      
      # Other steps

      - name: Export managed solution from build env
        uses: microsoft/powerplatform-actions/[email protected]
        with:
          tenant-id: ${{ env.TENANT_ID }}
          environment-url: ${{ env.BUILD_ENVIRONMENT_URL }}
          app-id: ${{ env.BUILD_APP_ID }}
          client-secret: ${{ env.BUILD_APP_SECRET }}
          solution-name: ${{ env.SOLUTION_NAME }}
          solution-version: ${{ github.event.inputs.release_version }}
          managed: true
          solution-output-file: ${{ env.SHIPPING_FOLDER }}/${{ env.SOLUTION_NAME }}.zip

Each time this runs, we are encountering this error:

Starting Solution Export...

Microsoft PowerPlatform CLI

Version: 1.7.5+g64e6bc4

Error: Exporting to a target version is not supported in this release.
    Exporting to a target version is not supported in this release.

Note: if we omit solution-version then the action completes successfully, but the managed solution package no longer has the desired version.

We don't have a great deal of experience with the Power Platform stack (or Microsoft tech in general), so this could be a simple misunderstanding on our part, but it seems that the solution-version action input doesn't appear to work as documented.

Not sure if this is documented anywhere but I'd like to be able to fail a job if the solution-checker returns medium severity issues.

When building Canvas Apps it is very easy to overlook the accessibility checker warnings which are raised as Medium severity warnings. I'd like to be able to ensure that we have quality gates in place so that developers cannot overlook this so failing the job will help enforce this.

If the solution file is specified, then the output can be defaulted to the solutionname.zip.

Running with an ubuntu-latest runner, the branch-solution action fails with the message:

Error: failed: Error: Cannot determine HEAD from remote: ...

Any plans on publishing the pac library as a separate npm package?

in addition to the already available username/password authentication (which is not MFA compatible when running in a non-interactive context like a GH action), a new version of the underlying pac CLI will also allow AppID (ServicePrincipal) / clientSecret authentication for actions

Work is already in progress, but no definite ETA yet

I'd like to see an action that enables us to automate the execution of tests written in Test Studio against Canvas Apps to provide some quality gates to ensure updates don't break existing functionality.

Can you add a 'latest' tag and 'v0' tag so that we can reference the latest version rather than a specific version eg:

uses: microsoft/powerplatform-actions/import-solution@latest

Team,
We are planning to upgrade the logo for all 13 GitHub Actions projects listed on the GitHub Marketplace to the official Microsoft logo.

We'd like to make this change by the end of May 2021.

Please let us know if you have any objection, otherwise we'll proceed.

https://github.com/microsoft/raft-action
https://github.com/microsoft/sarif-actions
https://github.com/microsoft/powerplatform-actions
https://github.com/microsoft/psscriptanalyzer-action
https://github.com/microsoft/vs-intellicode
https://github.com/microsoft/setup-msbuild
https://github.com/microsoft/ps-rule
https://github.com/microsoft/RichCodeNavIndexer
https://github.com/microsoft/playwright-github-action
https://github.com/microsoft/DevSkim-Action
https://github.com/microsoft/infersharpaction
https://github.com/microsoft/android-app-size-diff
https://github.com/microsoft/variable-substitution

Hello!
I am building upon the Github Actions PowerPlatform tutorial from the Microsoft Docs.
My goal is to use the check-solution action on the dev Dataverse environment. In this case, after the export-solution step.
When I run this action, the authentication step of check-solution works, but the actual command to upload the solution fails with:
Error: A configuration issue is preventing authentication - check the error message from the server for details. You can modify the configuration in the application registration portal. See https://aka.ms/msal-net-invalid-client for details. Original exception: AADSTS7000215: Invalid client secret is provided.

The link from the error message tells me to enable public client flows of the application in the Azure portal, which I enabled.

I also regenerated the secrets multiple times & the error persists.

When executing the pac commands locally with the same secrets and tenant information, the solution check is behaving as expected.

Local commands

1. Auth: pac auth create --name auth1 --url <env_url> --clientSecret <client_secret>--tenant <tenant> --applicationId <app_id>
2. Check: pac solution check --path <path_to_zip> -o output

Am I missing any configuration or step to get a successful check-solution action running? Thanks in advance!

I got this error once when I tried to import the solution for the very first time. The solution imported eventhough the workflow failed, and I did not get the error the second time I tried to import.

Hello,

All our actions for various export and import solutions have suddenly stopped working since 01/02. Event logs on win 2016 server VM shows a very generic error 'The program or feature "??\D:\actions-runner_work_actions\microsoft\powerplatform-actions\v0\dist\pac\tools\pac.exe" cannot start or run due to incompatibity with 64-bit versions of Windows. Please contact the software vendor to ask if a 64-bit Windows compatible version is available.'

After spending 2 nights trying to figure out the issue and using almost all version of releases, still no joy. Any help will be greatly appreciated.

Note: I have tried using all versions from 0.4.0 to 0.5.1 with the same result

There is no way to specify the --cloud parameter that the PAC CLI tool supports with the current action definitions. The result is that we cannot use GitHub actions with US GCC High and DoD Power Platform environments. Can we add an optional cloud parameter to each action that defaults to the public endpoint, but enables that to be overridden with other cloud endpoint values?

The current supported cloud types via the PAC tool are below,

Values: Public, Tip1, Tip2, UsGov, UsGovHigh, UsGovDod

Error: Unable to resolve action microsoft/powerplatform-actions@v0, repository not found on this server. If you want to use this action from GitHub.com, see the following documentation: https://docs.github.com/en/enterprise/admin/github-actions/managing-access-to-actions-from-githubcom

I'd like to see the ability to inject environment variables into a solution in a workflow that is deployed as a managed solution into a target environment, not sure if this is on the publish-solution or export-solution action.

When I tried to import the solution, I got the above issue. Is there a way to set a newer version while exporting the solution itself. Tried the current solution-version in export-solution, no luck either.

Is there a work around here..?

All the microsoft power platform Tasks are not working.

I'm using the pack-solution and import-solution actions to import an unmanaged solution from a GH repo to a dev environment. This is how I use the import-solution action:

- name: Import unmanaged solution to dev
      uses: microsoft/powerplatform-actions/import-solution@v0
      with:
        environment-url: ${{ env.DEV_URL }}
        app-id: ${{ env.APP_ID }}
        client-secret: ${{ secrets.CLIENT_SECRET }}
        tenant-id: ${{ env.TENANT_ID }}
        solution-file: out/solutions/${{ env.SOLUTION }}.zip
        run-asynchronously: true
        force-overwrite: true
        publish-changes: true

Most of the time this works as expected, but sometimes the action runs for an hour and then times out with Error: The HTTP request is unauthorized with client authentication scheme 'Anonymous'. But when I check the target environment, the solution has actually been imported and works just fine.

I've experienced this with different solutions and different environments. It's also happened with small solutions that usually only take a few minutes to import. Any ideas why this might be happening? It's a bit frustrating because every time this happens a full 60 minutes of run time get added to your billable GH actions minutes.

Hello,

I am using import-solution action with service principal authentication. The connection references dependencies are creates and configured before the import.
The flows are off after importing the solution despite the connection references are ok. This behaviour happen even the flows were on before importing a new version. Is it a expected behaviour?. How can we activated the flow automatically?

Thanks for your help

Do you have plans to provide OIDC federated auth support for service principles?

see https://docs.microsoft.com/en-us/azure/developer/github/connect-from-azure?tabs=azure-portal%2Cwindows#use-the-azure-login-action-with-openid-connect for more information

the azure login github action provides such functionality, associated docs: https://github.com/Azure/login#configure-a-service-principal-with-a-federated-credential-to-use-oidc-based-authentication

Running most actions (see https://github.com/jjkinsey/testing-popl-actions/runs/4536991605, https://github.com/jjkinsey/testing-popl-actions/runs/4536991736 for minimal examples) produces the error:

Error: failed: Error: Error parsing yaml file for unpack-solution: Error: ENOENT: no such file or directory '/home/runner/work/testing-popl-actions/testing-popl-actions/export-solution/action.yml'

This seems to be coming from this line, present in 14 actions:

The YamlParser class looks for the workflow YAML file but can't find it, as the working directory doesn't include actions when they're used normally from another repository (they're instead located under /home/runner/work/_actions/, at least is what I found in my testing; not sure if that's a stable interface or not).

This bug effects the following actions:

• backup-environment
• check-solution
• create-environment
• copy-environment
• delete-solution
• deploy-package
• download-paportal
• export-solution
• import-solution
• pack-solution
• unpack-solution
• update-solution-version
• upgrade-solution
• upload-paportal

Hello @davidjenni and team. I am attempting to use this template as part of the ALM Accelerator for Makers work being done by @devkeydet and the PowerCAT team and I found that I was unable to get it to run in an asynchronous manner for solutions that take longer than 2 minutes to import (which is quite common when you include a simple canvas app in a solution). See below for more details:

This is the error that is provided

This is my configuration

Let me know if I'm missing something here.

Thanks!

Hi,

We had our pipelines working nicely, however, importing the managed solution from Build > Production is continually failing with this error.

Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout.

Importing the unmanaged solution from Dev > Build works fine, it fails whilst trying to export to managed and import. Exactly where/why it's failing were unsure.

Action below - removed org-specific details.

name: release-solution-to-prod

prepare for releasing to prod:

convert solution to managed (using a build PowerPlatform environment for the conversion)

upload the solution to the GitHub artifacts and deploy to the PROD environment

on:
workflow_dispatch:
inputs:
# Change this value
solution_name:
description: 'name of the solution to worked on from Power Platform'
required: true
default: DummyName
#Do Not change these values
solution_shipping_folder:
description: 'folder name for staging the exported solution do not change'
required: true
default: out/ship/
solution_outbound_folder:
description: 'staging the unpacked solution folder before check-in do not change'
required: true
default: out/solutions/
solution_source_folder:
description: 'folder name to be created and checked in do not change'
required: true
default: solutions/
solution_release_folder:
description: 'folder where the released binaries are going to be hosted do not change'
required: true
default: out/release
release:
types: [created]

env:
#edit your values here
BUILD_ENVIRONMENT_URL: 'https://xxx.crm6.dynamics.com'
PRODUCTION_ENVIRONMENT_URL: 'https://xxx.crm6.dynamics.com'
CLIENT_ID: 'xxxxxx'
TENANT_ID: 'xxxxxxx'

jobs:
convert-to-managed:
runs-on: windows-latest
# or you can say runs-on: ubuntu-latest
env:
RUNNER_DEBUG: 1

steps:
- uses: actions/checkout@v2
  with:
    lfs: true

- name: Pack solution
  uses: microsoft/powerplatform-actions/pack-solution@v0
  with:
    solution-folder: ${{ github.event.inputs.solution_source_folder}}/${{ github.event.inputs.solution_name }}
    solution-file: ${{ github.event.inputs.solution_outbound_folder}}/${{ github.event.inputs.solution_name }}.zip
    solution-type: Unmanaged

- name: Import solution as unmanaged to build env
  uses: microsoft/powerplatform-actions/import-solution@v0
  with:
    environment-url: ${{env.BUILD_ENVIRONMENT_URL}}
    app-id: ${{env.CLIENT_ID}}
    client-secret: ${{ secrets.PowerPlatformSPN }}
    tenant-id: ${{env.TENANT_ID}}
    solution-file: ${{ github.event.inputs.solution_outbound_folder}}/${{ github.event.inputs.solution_name }}.zip
    force-overwrite: true
    publish-changes: true
    run-asynchronously: true

- name: Export solution as managed
  uses: microsoft/powerplatform-actions/export-solution@v0
  with:
    environment-url: ${{env.BUILD_ENVIRONMENT_URL}}
    app-id: ${{env.CLIENT_ID}}
    client-secret: ${{ secrets.PowerPlatformSPN }}
    tenant-id: ${{env.TENANT_ID}}
    solution-name: ${{ github.event.inputs.solution_name }}
    managed: true
    solution-output-file: ${{ github.event.inputs.solution_shipping_folder}}/${{ github.event.inputs.solution_name }}.zip

- name: Upload the ready to ship solution to GH artifact store
  uses: actions/upload-artifact@v2
  with:
    name: managedSolutions
    path: ${{ github.event.inputs.solution_shipping_folder}}/${{ github.event.inputs.solution_name }}.zip

release-to-staging:
needs: [ convert-to-managed ]
runs-on: windows-latest
env:
RUNNER_DEBUG: 1

steps:
- uses: actions/checkout@v2
  with:
    lfs: true

- name: Fetch the ready to ship solution from GH artifact store
  uses: actions/download-artifact@v2
  with:
    name: managedSolutions
    path: ${{ github.event.inputs.solution_release_folder}}
- name: Import solution to prod env
  uses: microsoft/powerplatform-actions/import-solution@v0
  with:
    environment-url: ${{env.PRODUCTION_ENVIRONMENT_URL}}
    app-id: ${{env.CLIENT_ID}}
    client-secret: ${{ secrets.PowerPlatformSPN }}
    tenant-id: ${{env.TENANT_ID}}
    solution-file: ${{ github.event.inputs.solution_release_folder}}/${{ github.event.inputs.solution_name }}.zip
    force-overwrite: true
    publish-changes: true
    run-asynchronously: true

I can use "import-as-holding" argument to import managed solution as holding, but "Apply Upgrade" does not seem to be happening and there is no action to do this.

Hello, I'm fairly new to GitHub Actions so I'm not sure if this is an actual problem, or if it's even possible.

We are currently experimenting with GitHub Actions and have a workflow set up which is to export a solution from DEV into TEST, which I copied from these example workflows: https://github.com/microsoft/powerplatform-actions-lab/tree/main/sample-workflows

In this solution we have:

• Canvas App
• Simple flow that sends an email notification to myself
• Connection reference for the "Notification" in that flow

The solution export and import is working fine, but when we run the flow we get this error message:

Are we missing something in the workflow that will re-connect the connection references after import so that flows successfully run?

I know that when you export/import a solution from PowerApps itself, it will prompt you about connections, but because we're bypassing this stage is this the problem? We've also attempted this with an Azure DevOps pipeline and got the same result.

Thank you.

follow-up issue from #18

The listed inputs for the upgrade-solution action do not include inputs for service principal authentication.

Currently, this only throws a warning, but still successfully upgrades the solution using app-id, client-secret, and tenant-id.

A sample of this behavior can be found here.

Should be fixed by just updating upgrade-solution/action.yml.

Hi,

I'd like to achieve a clean build (zero-warning strategy). The current actions like "Power Platform Who Am I", "Power Platform Export Solution", "Power Platform Export Solution", "Power Platform Set Solution Version" produce warnings like

##[warning]The names of some imported commands from the module 'Microsoft.Xrm.WebApi.PowerShell' include unapproved verbs that might make them less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Get-Verb.

Can you please ensure, that no general warnings are exposed to the Azure pipeline?

Thanks,
Alexander

Using release 0.5.1 on Ubuntu runners. See here: https://github.com/jjkinsey/testing-popl-actions/runs/5071949865?check_suite_focus=true

Also tested on other actions, e.g. WhoAmI, but this was what I had public and handy.

Run microsoft/powerplatform-actions/[email protected]
  with:
    solution-file: out/solution.zip
    solution-folder: src
    solution-type: Unmanaged
    overwrite-files: true
unpack-solution:
  loading action yaml file: /home/runner/work/_actions/microsoft/powerplatform-actions/0.5.1/unpack-solution/action.yml
  Calling pac cli inputs: solution unpack --zipFile /home/runner/work/testing-popl-actions/testing-popl-actions/out/solution.zip --folder /home/runner/work/testing-popl-actions/testing-popl-actions/src --packageType Unmanaged --allowDelete true --allowWrite true --clobber true
  Error: /home/runner/work/_actions/microsoft/powerplatform-actions/0.5.1/dist/pac_linux/tools/pac: 1: version: not found
  Error: /home/runner/work/_actions/microsoft/powerplatform-actions/0.5.1/dist/pac_linux/tools/pac: 1: version: not found
  Error: /home/runner/work/_actions/microsoft/powerplatform-actions/0.5.1/dist/pac_linux/tools/pac: 2: oid: not found
  Error: /home/runner/work/_actions/microsoft/powerplatform-actions/0.5.1/dist/pac_linux/tools/pac: 2: oid: not found
  Error: size: '138736': No such file
  Error: size: '138736': No such file
  Error: error: 1
  Error: error: 1
  Error: failed: /home/runner/work/_actions/microsoft/powerplatform-actions/0.5.1/dist/pac_linux/tools/pac: 1: version: not found
  /home/runner/work/_actions/microsoft/powerplatform-actions/0.5.1/dist/pac_linux/tools/pac: 2: oid: not found
  
  size: '138736': No such file
  
  Error: failed: /home/runner/work/_actions/microsoft/powerplatform-actions/0.5.1/dist/pac_linux/tools/pac: 1: version: not found
  /home/runner/work/_actions/microsoft/powerplatform-actions/0.5.1/dist/pac_linux/tools/pac: 2: oid: not found
  
  size: '138736': No such file
  
  Error: failed: Error: /home/runner/work/_actions/microsoft/powerplatform-actions/0.5.1/dist/pac_linux/tools/pac: 1: version: not found
  /home/runner/work/_actions/microsoft/powerplatform-actions/0.5.1/dist/pac_linux/tools/pac: 2: oid: not found
  
  size: '138736': No such file
  
  Error: failed: Error: /home/runner/work/_actions/microsoft/powerplatform-actions/0.5.1/dist/pac_linux/tools/pac: 1: version: not found
  /home/runner/work/_actions/microsoft/powerplatform-actions/0.5.1/dist/pac_linux/tools/pac: 2: oid: not found
  
  size: '138736': No such file

For larger projects, some solutions will go past 60 minutes which is set as a default in pac. However it is possible to pass other value this way:

-max-async-wait-time: Maximum asynchronous wait time in minutes. Default value is 60 mintues (alias: -wt)

Could you please make use of this existing functionality and expose an attribute to set this value? It would be very much appreciated.

I am using the following

- name: import-manage-solution-to-environment
uses: microsoft/powerplatform-actions/import-solution@main #using @main for now because convert-to-managed isn't officially released, therefore won't be in v0
with:
environment-url: ${{ github.event.inputs.environment_url}}
tenant-id: ${{ secrets.tenant_id }}
app-id: ${{ secrets.client_id }}
client-secret: ${{ secrets.client_secret }}
solution-file: ${{ runner.temp }}/${{ github.event.inputs.solution_name }}/artifact/${{ github.event.inputs.solution_name }}.zip
force-overwrite: true
convert-to-managed: true

I am getting the following error:
Error: CanvasApp import: FAILURE: A managed solution cannot overwrite the CanvasApp component 'dkdt_cvdeleteme_59c95' with Id=5ccf3fd0-0117-4c1e-9d35-6fbbd82e2693 which has an unmanaged base instance. The most likely scenario for this error is that an unmanaged solution has installed a new unmanaged CanvasApp component on the target system, and now a managed solution from the same publisher is trying to install that same CanvasApp component as managed. This will cause an invalid layering of solutions on the target system and is not allowed.

However, when I do this with pac directly, it works as expected. Full source code is here:
https://github.com/devkeydet/pva-alm/blob/d7b47d0f2bc99f113bcd84e162295cc67de42710/.github/workflows/delete-unmanaged-solution-and-components-from-environment.yml#L121

I am trying to setup Microsoft Graph connectors for network file share

I created a demo tenant.
Login in azure portal with my demo tenant credentials.
Registered an app and grant permission as per this document https://docs.microsoft.com/en-us/microsoftsearch/on-prem-agent

After this I installed GCA from https://aka.ms/GCAdownload, then login in GCA using my demo tenant credential. Now when I am trying to register GCA with AppId and client secret of the App registered in above step, I am getting error

Hi team,

I thought it would be great to use the environment-url output provided in the create-environment action but face an unexpected issue during my first test.

It seems the value in the environment-url output is "masked" (ex: https://***19***/).

In my case, I tried to put the value of the environment-url output in a job output to use it in other places in my workflow but got the following message: Skip output 'dev_environment_url' since it may contain secret.

Is it normal that the value of the output is "masked"?
If yes, do you think you could provide a way to have the unmasked value so we can use it in the workflow? (ex: mask-aws-account-id input in aws-actions/configure-aws-credentials)

Thank you in advance for your help.

Getting the following error connecting to an environment with MFA enabled:

export-from-dev
error: 1: Microsoft PowerApps CLI

Version: 1.5.3+gdf82e3f

Error: AADSTS50076: Due to a configuration change made by your administrator, or because you moved to a new location, you must use multi-factor authentication to access

Hi There,

Fairly new to github actions. Have been using the ALM lab yml code (release-solution-to-prod). When executing a release I get the following error when packing the solution. Seems the pack/release solution yml is looking in the wrong location. Running the workflow manually works fine. It's only when the workflow is triggered from a release it fails like this.

Any help would be greatly appreciated.

Thanks,
James

I would like to know if there is any plan to include set solution version action or a similar feature of "Set Solution Version" task provided by Power Platform Build Tools.
Thanks in advanced

Hello,

Most of the docs say "Service Principal Auth will be supported late 2020". Has it been implemented? If so, how do we set it up?

Thank you,

I am trying to develop a CI/CD pipeline, however sometimes the error in the attached picture happens from time to time. After some retries the issues seems to disappear and the following runs work fine.

Exception Id:345b4038-f620-43df-9f32-4e324075d644

Is there any help I can get?
Thank you in advance.

i do not see a way within the actions here to Reg a plugin or its steps (add or remove them)

if i am incorrect please point me to the right place.

Do these Actions support PowerApps in GCC? Are there any known limitations? Thanks!