In Octopus, an empty unscoped variable is the standard way to model a default that scoped values override, like a log server that only exists in Prod. Expect the editor warnings and do not chase them; the pattern is intentional even though the warnings cannot be suppressed.

Context: From GitHub issue OctopusDeploy/Issues#4008. Leaving a variable empty and unscoped is the documented pattern for a default that scoped values override (empty everywhere, real value in Prod). The issue: the variable editor shows a non-suppressible warning on every such empty variable, so projects that use the pattern heavily look like something is badly wrong. The warning is valid in general, since an empty value can break a deployment, but the pattern itself is legitimate.