Closed pminnebach closed 4 years ago
Not in a position to test myself, but interested to know.
Does the function return the arguments: Get-UAPowerShellVersion
If you add a new PS version via the function, does it stick: New-UAPowerShellVersion
Just wondering if it's a disconnect between UD and the UA server.
Nope - just wasn't implemented properly.
Currently testing fixes - will be merged shortly
Merged!
It still isn't solved for me.
I still can't edit the arguments from the dashboard. But when i add a new one via the powershell gui, it does show the correct argument.
Also, with a fresh setup, it shows my complete $profile output.
I verified all this by deleting the modules completely and the localappdata folders.
@leeberg
@pminnebach - right you are!
Sorry I got the fixes merged but it's not in a new build of UA yet - I'll keep this open and post once that build is release.
I can fix that profile thing. We get the PS version by launching PS and running $PSVersionTable but we must not be passing -NoProfile.
Unless you got that too @leeberg ?
NVM: It's not fixed yet. Will fix.
Going to mark this as resolved since it's committed. I've updated the changelog to include unreleased changes: https://github.com/ironmansoftware/universal-automation/blob/master/CHANGELOG.md
Describe the Issue
When i want to modify the config of the powershell versions to add an argument
-noprofile
, it doesn't save the argument. The same happens when adding a new powershell version. The Version and Path are saved, but not the argument.Expected behavior
It should save the argument. :)
Screenshots
Script Sample
Attempt to attach sample code that will allow others to reproduce the issue. NOTE: Generally speaking this is the MOST EFFECTIVE way to have your issue resolved.
Version Information