guyben 557984bb75 Add support G-Suite group whose members have ADMIN access to registrar console ... After this CL, "support" accounts (accounts that are part of the "support" G-Suite group) will the same access to the registrar console as GCP "admins". However, they don't won't have access to the GCP project itself. We could give them their own Role in the future (say SUPPORT) and give them different access than "admins", but right now we don't need it and YAGNI or something :) NOTE: we identify users by their email (they need to be logged in to a google account). I don't know if that's best practice, since I guess different google accounts might have the same email address. However, G-Suite groups' membership is by email so there's not much we can do about it if we want to use G-Suite groups. ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=220804273		2018-11-12 14:51:40 -05:00
..
default-config.yaml	Add support G-Suite group whose members have ADMIN access to registrar console	2018-11-12 14:51:40 -05:00
nomulus-config-alpha.yaml	Move the environment configuration YAML files into the main JAR	2017-02-06 16:46:52 -05:00
nomulus-config-crash.yaml	Move the environment configuration YAML files into the main JAR	2017-02-06 16:46:52 -05:00
nomulus-config-local.yaml	Move the environment configuration YAML files into the main JAR	2017-02-06 16:46:52 -05:00
nomulus-config-production-sample.yaml	Add support G-Suite group whose members have ADMIN access to registrar console	2018-11-12 14:51:40 -05:00
nomulus-config-production.yaml	Move the environment configuration YAML files into the main JAR	2017-02-06 16:46:52 -05:00
nomulus-config-qa.yaml	Move the environment configuration YAML files into the main JAR	2017-02-06 16:46:52 -05:00
nomulus-config-sandbox.yaml	Move the environment configuration YAML files into the main JAR	2017-02-06 16:46:52 -05:00
nomulus-config-unittest.yaml	Add octothorpes to disclaimer in exported reserved list	2018-09-08 00:18:19 -04:00