limit logins on staging servers

[shaneknapp]

only allow datahub staff for all staging server logins. we can also include (or add at a later date) any others who help us deploy/test/etc.

• update cookiecutter templating in datahub/deployments/template
• test on the new dev hub (create dev hub for us to play with #4443)
• documentation!
• add a new hub.jupyterhub.config.Authenticator.allowed_users block in staging.yaml for each hub with all staff + contribs

https://jupyterhub.readthedocs.io/en/stable/getting-started/authenticators-users-basics.html#create-a-set-of-allowed-users-allowed-users

[ryanlovett]

@shaneknapp We usually ask instructors and GSIs to test on staging before merging changes to prod. How would they be able to test otherwise?

[shaneknapp]

potentially, we can add them manually. also we could test the see if we can have more than one group applied here. if this turns out to be a rabbit hole not worth exploring we can just implement this on the dev hub.

…

On Mon, Apr 10, 2023 at 10:34 AM Ryan Lovett ***@***.***> wrote: @shaneknapp <https://github.com/shaneknapp> We usually ask instructors and GSIs to test on staging before merging changes to prod. How would they be able to test otherwise? — Reply to this email directly, view it on GitHub <#4453 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAMIHLBAYNXF7EHRPTWZ6ULXARACTANCNFSM6AAAAAAWZFZQYY> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[balajialg]

* [ ]  add a new hub.jupyterhub.config.Authenticator.allowed_users block in `staging.yaml` for each hub with all staff + contribs

https://jupyterhub.readthedocs.io/en/stable/getting-started/authenticators-users-basics.html#create-a-set-of-allowed-users-allowed-users

This would be an awesome use case when #4180 gets implemented