8.11.2 | Unable to load a custom PS repo to script environments

[mayank_goyal]

I started using the vRO 8.11.2 and was able to test custom repos for Node.js and Python (https://cloudblogger.co.in/2023/03/29/vro-8-11-2-add-a-custom-repository-to-script-environment-cb101...), worked fine for me. But for PowerShell, it doesn't seem to be working.

In the below example, I am using a PS module for ServiceNow (https://github.com/Snow-Shell/servicenow-powershell). I have added a repository.

Added the dependency

But the downloading fails as it couldn't find the repo.

The same process seems to work with node and python though.

[mayank_goyal]

I think it's not an issue. I am not doing it correctly.

It would require me to host a local PS repository and then it should work fine (something like this -> https://learn.microsoft.com/en-us/powershell/scripting/gallery/how-to/working-with-local-psrepositor...). Will keep it posted here.

[paul_xtravirt]

Hi, did you manage to get this working? I am suffering from the same issue now with 8.13. I setup a PowerShell repo privately with ProGet but got the same issue as you were getting, when I host the packages myself. From native Powershell, it works fine!

[jomwilliams]

Hi @paul_xtravirt. Does your private PS repo happen to be an HTTPS site secured with a self signed or an internally trusted cert? If so, I recently opened a case with VMware support, and apparently even though you can add a private repo, currently you cannot add a private CA certificate that may secure that repo site. This will cause the download to fail with a similar message that @mayank_goyal received in regards to being unable to resolve the source.

I asked that a feature request be opened to allow us to add private CA certs to Orchestrator and was told that it should be available in a future release. However, I am unsure of the exact timeframe. In the meantime, there appears to be no workaround for adding packages from private repos with this set up.

[paul_xtravirt]

Hey there, thanks for the comment 🙂 I have actually been attempting with an http site, not https - is https a requirement? I am finding the documentation around all of this pretty poor unless my ability to search has declined this year!

[jomwilliams]

Yeah agreed, documentation on this functionality is sparse at best. From what I was told by VMware support, HTTP was the only supported config for private repositories, due mostly to the certificate issue, so HTTP should work from my understanding. However, I currently do not have a private repo using HTTP, so unfortunately I cannot confirm how it might work.