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.