Permissions: Variables

Hello all

I was really happy to read that the variables will get more detailed permissions (granularity “environment”) with current release ( 1.1.1.1404, Released on Tuesday, October 30, 2012) because it was one of the things I was really missing.

Today I updated the octopus server and the corresponding rules - so that “Developer” do not see “Production”-Variables anymore.
Problem: As soon as I limited the Developer’s “View-Variables Permission” to a specific environment they can’t access the variables-table anymore! (and therefore cannot edit “Developer” environment specific variables also)

Is this really the intended behavior?

Kind regards,
Beat

Hi Beat,

Thanks for getting in touch, this is a known issue and I’ll have a fix out shortly. As a workaround, you can remove the ‘deny’ permissions for ‘all environments’, and add an individual deny permission for each environment.

Hope that helps,

Paul

Hello Paul,

Ah cool - that way it works! Thank you very much :slight_smile: the permissions get a bit clumpy now, but as long as I’m testing that’s perfect enough.
The ‘hidden’ settings are cool for me, even better than I expected (I expected to not see any variable “rows” which I should not see). But now developers may see that other environments may miss variables.
That’s great :slight_smile:

Kind regards,
Beat

Any update on this. It seems that viewing/editing variables is tied to the ‘Edit Project’ permissions, which sort of makes sense. However for our production control folks we don’t want them messing around with the project steps and the project settings. Just the variables.

Hi David,

The issue reported in this post was fixed a while ago. The one you are describing is a little different, but I’ll be fixing it today with a goal of releasing it in a release early next week.

Paul