Change hard coded execution policy in power shell task

[fhanggi]

Question, Bug, or Feature?
Type: Question

Enter Task Name: PowerShellV2

Environment

• Server - Azure Pipelines or TFS on-premises? TFS on premises

  • If using TFS on-premises, provide the version: 2019

• Agent - Hosted or Private: Private

Issue Description

We have a need to move all of our powershell scripts to a different server than the build server. We want to execute them from that new server. The script path is set to this
\builddev\Shared\PowerShell\COVReactInstall.ps1

We are getting UnauthorizedAccess errors now .
We found out that the issue is that this powershell task hard codes the execution policy to Unrestricted

$arguments = "-NoLogo -NoProfile -NonInteractive -ExecutionPolicy Unrestricted -Command "$executionOperator '$($filePath.Replace("'", "''"))'""

We would like to change it to ByPass.
How can this be done? We didn't see a way to pass in powershell arguments to this task

Thank you
Fabian

[WenceyWang]

Is there any progress on this issue? or should I submit a pr to add the inputs?

[anatolybolshakov]

Hi @WenceyWang sorry for the delay - we are currently working on more prioritized tickets at the moment, but will get back to this one once be able to. Yes, feel free to submit the PR if you would like to contribute, thanks!

[github-actions]

This issue is stale because it has been open for 180 days with no activity. Remove the stale label or comment on the issue otherwise this will be closed in 5 days

[fhanggi]

Currently we had to deploy all of our powershell scripts to all build servers as a workaround.

If we could have an update on this it would be nice.

[github-actions]

This issue is stale because it has been open for 180 days with no activity. Remove the stale label or comment on the issue otherwise this will be closed in 5 days

[fhanggi]

Currently we had to deploy all of our powershell scripts to all build servers as a workaround.

If we could have an update on this it would be nice.

[github-actions]

This issue is stale because it has been open for 180 days with no activity. Remove the stale label or comment on the issue otherwise this will be closed in 5 days

[WenceyWang]

If we could have an update on this it would be nice.

[github-actions]

This issue is stale because it has been open for 180 days with no activity. Remove the stale label or comment on the issue otherwise this will be closed in 5 days

[fhanggi]

Can we have an update please?