I want the installer to also scaffold a workspace, so I tried adding the parameter to the one-liner:
irm https://sdods.com/install.ps1 | iex -Workspace C:\my-testsPowerShell does not like that, and every variation I have tried either errors or installs with the defaults and silently ignores the parameter. What is the correct form?
Accepted answer
iex cannot forward parameters — it evaluates a string, and the parameters you type belong to iex itself, not to the script inside the string. Build a script block instead and call it:
& ([scriptblock]::Create((irm https://sdods.com/install.ps1))) -Workspace C:\my-tests -Mcp claudeThat is the documented form and it takes all the parameters: -Version, -Dir, -BinDir, -Pm, -Browsers, -Workspace, -Source, -Mcp, -ModifyPath, -Yes, -Uninstall, -DryRun, -VersionCheck, -Help.
The other option, and the better one if this goes in a runbook where someone will read it later, is to download it first:
irm https://sdods.com/install.ps1 -OutFile install.ps1
.\install.ps1 -Workspace C:\my-tests -Browsers chromiumEvery parameter also has an environment variable, which is usually cleaner in CI than either form:
$env:SDODS_WORKSPACE = "C:\my-tests"; $env:SDODS_BROWSERS = "chromium"; $env:SDODS_YES = "1"
irm https://sdods.com/install.ps1 | iexHave the same question?
Ask it with the command you ran and the output you got, and it will be answered here.
Ask a question