Acessing Power Platform CLI - POWERPLATFORMTOOLS_PACCLIPATH

[fowl2]

The tool installer task seems to make the Power Platform CLI available under these paths:

On Linux: $(POWERPLATFORMTOOLS_PACCLIPATH)/pac_linux/tools/pac
On Windows: $(POWERPLATFORMTOOLS_PACCLIPATH)/pac/tools/pac.exe

This isn't the most convenient, but very very useful!

Is it possible to have the tool installer (possibly optionally) add this directory to PATH? This way we could just use pac in our scripts.

I'd also suggest a "Power Platform CLI Task" for easier access to functionality that doesn't yet have a dedicated task.

[BetimBeja]

@fowl2 (and 👀 @rpothin)
In Azure DevOps you can use the Prepend Path logging action. Examples:

• windows agent:

- pwsh: |
    $pac = Join-Path $env:POWERPLATFORMTOOLS_PACCLIPATH pac tools
    echo "##vso[task.prependpath]$pac"
  displayName: 'Add PAC to Path' 

• linux agent:

- pwsh: |
    $pac = Join-Path $env:POWERPLATFORMTOOLS_PACCLIPATH pac_linux tools
    echo "##vso[task.prependpath]$pac"
  displayName: 'Add PAC to Path' 

It will add the directory to PATH for all the subsequent tasks, and you can easily use pac in a script.

I haven't tested GitHub Actions yet. But the same should be achieved by adding to GITHUB_PATH environment variable.

UPDATE 2023-12-31:
In GitHub Actions you can use the following step (Windows and Linux) to Add a System Path:

- name: Add pac to PATH
  shell: pwsh
  run: |
    $pac = (Get-Item "$env:POWERPLATFORMTOOLS_PACPATH").Directory.FullName;
    "$pac" | Out-File -FilePath $env:GITHUB_PATH -Append

[tehcrashxor]

As of v2.0.69 (via PR #869), the Power Platform Tools Installer task has the option to add PAC to the PATH as well.