Page MenuHomePhabricator

Implement access control via Puppet
Open, LowPublic5 Estimated Story Points

Description

A/C
GIVEN Esha has created an environment
WHEN the environment has spun up and is ready to use
THEN Esha should have SSH access to her instance
AND members of the catalyst project should have SSH access to her project
AND no one else should have SSH access to her project

GIVEN Esha's team mate has been granted access to Esha's environment
WHEN he attempts to SSH into Esha's environment
THEN he should be able to log in
AND he shouldn't have to wait more than a couple of minutes before gaining access

For this, operations-puppet/production/modules/profile/manifests/ldap/client/labs.pp needs to be modified so that access can be managed on a per-ldap-user basis, in addition to the current per-ldap-group setup. More details in T349637: EXPLORE restricting users' access to specific test environments

Event Timeline

Slst2020 set the point value for this task to 5.
thcipriani subscribed.

Assigning a lower priority based on the Catalyst workboard check-in today.

Work for this has yet to begin, and given the focus on the test engineer use-case, this task may have a lower priority.

We now have support for unmanaged (unpuppetized) instances, so this should no longer be necessary.