When trying to create the file vaults.ps1 for connecting to Azure Key Vault on startup, we are running into the following error.
File F:\UniversalAutomation\Repository.universal\vaults.ps1 cannot be loaded because running scripts is disabled on this system. For more information, see about_Execution_Policies at about_Execution_Policies - PowerShell | Microsoft Learn.
Has anyone ran into this issue when restarting PSU?
We’ve got a fix coming for this in v5.4.2 and v5.5.0. It might be possible to configure your execution policy in a way to avoid this but we’ll be adding a bypass.
Thank you Adam. I’ll let our security team know that feature may be available in the future. For now I’ll create a report to let us know if a secret is added to the wrong vault.
If I create a script to read the contents of vaults.ps1 that won’t trigger the file watcher right?