Closed fMichaleczek closed 3 years ago
Because there is also a proxy , a vpn and a general problem that need profile.ps1, I will check more.
That was a problem linked to VPN. Network state change between my sample generation,that affect PSRepository policy too (I love Authentificated Proxy).
Mostly because this kind of proxy use NTLMv2 or Kerberos (because ZeroLogon patch etc..), I need this :
[System.Net.WebRequest]::DefaultWebProxy.Credentials = [System.Net.CredentialCache]::DefaultNetworkCredentials
(Maybe a security issue to add by default in the bootstrap, I'm not enough expert with this part of dotnet API)
Details of the scenario you tried and the problem that is occurring
Install this module, create a sample, the script build.ps1 stop and Windows PowerShell user's configuration of PSRepository is broken. (maybe SourceLocation is come back to V2 ? I dont remember because the insane switch between nuget for C# and nuget for PowerShell) I can't provide previous configuration, it's gone!
Verbose logs showing the problem
Suggested solution to the issue
Add a better layer to package source management. The module break my "enterprise" computer configuration. It's a barrier to ask people to test it after I test it. Not important at this point, because it's a code for "advanced users" but this kind of details should be resolved for the good of all.
The DSC configuration that is used to reproduce the issue (as detailed as possible)
N/A
The operating system the target node is running
Version and build of PowerShell the target node is running
Version of the DSC module that was used ('dev' if using current dev branch)
N/A