We have been cleaning up our roles as we improve our infrastructure and app deployments. We had some roles that we found we no longer needed so we removed them from all our machines. However, we were using those roles to scope some variables. It seems that when the role is removed from all machines there is still some phantom scope on the variables that were using those roles.
We are using Octopus 3.4.5
Steps to reproduce:
- Create a role on a machine
- Create a variable scoped to that role
- Remove the role from all machines
Expected behavior:
The scope is removed from any variables using the role that was removed
Actual Behavior:
The scope is removed but not in a good way. See the attached image. There still seems to be some scope association with a “blank” role. Note the barely visible X icon to remove it in the image. The problem is that because it has the phantom role the variable will not be applied anywhere and default values will probably be used.
