Scoping library variables based on Project Group.
We have common variables used by all the projects in a project group. The only way to share them across the projects (currently) is to place these variables in the “Library Variables”. Unfortunately, it exposes these variables to everyone else and we really need it to be restricted to just the group.
Tony
shared this idea
-
Jerome Scholefield
commented
Hi,
I decided to log a new problem as you flagged this many moons ago.
https://help.octopusdeploy.com/discussions/problems/68973-securing-library-variable-setsI have been advised that something called spaces is being looked into.
https://github.com/OctopusDeploy/Specs/blob/master/Spaces/index.md
-
Jerome Scholefield
commented
This feature should be core functionality. In an enterprise environment where security is strict but you want to empower the developers to run their own projects. You want to setup a team and assign them to a project group so they can manage their projects end to end. And not being able to lock down library variables sets to a project group means you get a lot of duplication, wasted time and its very error prone.