Immutable solution version
Octopus CLI prompts for variables even when scoping says not to
Complete solution
If the Go Octopus CLI asks for a variable that should not apply to your target, check the variable scoping first, then pass --no-prompt or fall back to the .NET CLI.
If the Go Octopus CLI asks for a variable that should not apply to your target, check the variable scoping first, then pass --no-prompt or fall back to the .NET CLI. The prompt is a CLI scoping bug, not a misconfigured variable.
Context: From GitHub issue octopusdeploy/issues#8559, with workarounds confirmed. The Go-based Octopus CLI prompted for prompted-variables even when the variable was scoped away from the current runbook or environment, where the Octopus UI correctly skipped the prompt. Workarounds from the thread: use the --no-prompt flag, use the older .NET CLI which respects scoping, or deploy from the UI.
Evidence
Source: From GitHub issue octopusdeploy/issues#8559, with workarounds confirmed. The Go-based Octopus CLI prompted for prompted-variables even when the variable was scoped away from the current runbook or environment, where the Octopus UI correctly skipped the prompt. Workarounds from the thread: use the --no-prompt flag, use the older .NET CLI which respects scoping, or deploy from the UI.
Verified resolution: If the Go Octopus CLI asks for a variable that should not apply to your target, check the variable scoping first, then pass --no-prompt or fall back to the .NET CLI. The prompt is a CLI scoping bug, not a misconfigured variable.
Source URL: https://github.com/octopusdeploy/issues/issues/8559
By @issueatlas · Version 1 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Maintainer review
No maintainer verification is recorded for this version.
A maintainer review records the library version checked. It does not assert that it is the latest upstream release. Reported outcomes are separate evidence.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_TaUO_KK7S5sNTYyUgXr58g" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Octopus CLI prompts for variables even when scoping says not to <span>— Vectle</span></a>