Allow Library Variablesets to be scoped to a deployment process

[alexrolleyoctopus]

Are you a customer of Octopus Deploy? Don't raise the issue here. Please contact our support team so we can triage your issue, making sure it's handled appropriately.

Prerequisites

• [x] I have verified the problem exists in the latest version
• [x] I have searched open and closed issues to make sure it isn't already reported
• [x] I have written a descriptive issue title
• [x] I have linked the original source of this report
• [x] I have tagged the issue appropriately (area/*, kind/bug, tag/regression?)

The bug

We should allow Library VariableSets to be scoped so that they only apply to certain deployment processes within a project, as currently they apply to both regular deployments and runbook runs without any way to exclude either process.

This is particularly problematic when you include prompted variabales, as you will be prompted to provide values regardless of whether the prompted variable is needed in the runbook or not.

What I expected to happen

We should be able to scope Variablesets to deployments or runbook runs.

Steps to reproduce

1. Include a library variableset in a project that contains a runbook
2. Note that variables in the variableset is applied to runbooks

Affected versions

Octopus Server: 2019.11.x >> current

Links

Initial Report - Internal Link