Security group per environment

[sunsided]

I was noticing that the security groups feature might be a bit too restrictive. A feature that would be very interesting to us would be the limitation of security groups per environment (say, lowest context level). Essentially, DevOps only should be able to decrypt credentials for production and staging environments, whereas integration environment credentials should/could be public to all developers, and developer machine credentials should only be visible to the individual developer.

In essence, this would mean that a group should be applied to a specific context level rather than a specific key. Is that possible / possible to implement?

[earslanagic]

I think you're completely correct. It should be almost the same as the access rule service, giving you the ability to set security group based on context (partial or fully specified), and key (partial or fully specified).

Does that make sense to you?

If so, we can figure out the timeline when we could put this out by.

[sunsided]

Yes, absolutely. That does sound perfect.

[UmutMuslu]

Hi,

I have the same problem. I'd like to create a different JDBC connection string for different environments. All I need is to use the same key but different security groups.

@earslanagic, do you have a timeline for this improvement?

Thanks,

Umut.

[edoarsla]

We are starting to work on this feature and it will be in the next release. We're planing on early December.

[blazmanx34]

Could you tell us the implementation state of this enhancement ?
This feature would make ConfigHub really better.