OctopusDeploy
Improve variable change detection
Currently variable change detection doesn't tell us what has changed just that something has changed. There are cases where we need to know if the change is from a sensitive variable or not, e.g. in a CaC project where depending on if it's a sensitive variable change we either save to the db or create a commit.
An interesting use-case/problem was raised by one of our partners.
Imagine a requirement to add or change only a sensitive variable in a project that is both version-controlled and has branch protections enabled in the project. The Web portal makes you commit the change to the sensitive variable to a new branch, despite the variable value being saved in the database.
When the new branch has been pushed (with no meaningful change), the user is unable to create a PR since there are no changes, and is left confused trying to work out how to get their variable value merged to the main branch.
However, as the variable is stored in the database and effectively "shared" across branches, the new value is actually already available to use in a new release on the main branch (or any runbook runs)
