Add script console permissions
We need an ability to allow specific users access to the script console based on their environment permissions. So if we could have the ability to assign users/teams access to the script console, and then only allow them to use it based on their environment permissions that would solve some problems.
Source: http://help.octopusdeploy.com/discussions/questions/2242
Vanessa Love
shared this idea
-
Michael
commented
Script Console makes auditing so handy. Would love to be able to allow devs to use this in non-prod environments. Can we constrain by Environment and AD group?
-
Amjad Khoja
commented
We have a need to open the option of script console it would be good to separate out from Administrator
-
Graham Russell
commented
It would be really useful to allow access for this to some environments (dev/test) but restrict live.
-
Jai Kang
commented
I feel like this is exposing an implementation detail ( Deployment : ITask ).
As a user, it seems pretty counter intuitive that I couldn't restrict users to simply "deployments" given that running server tasks is seemingly advertised as "for administrators". It puts a great onus on administrators to be extra careful about collecting artifacts and making sure to delete them etc.
-
AdminRobert Erez
(Admin, Octopus Deploy)
commented
Given that running step templates are a feature built on top of the script console, it may make sense to additionally add a permission to allow step templates to be run without requiring admin permissions.
source: http://help.octopusdeploy.com/discussions/questions/10911