We've mostly standardized on naming any / all project resources after the GitHub repository, but Google APIs projects remain a Wild West, which makes it hard to keep track of where relevant credentials are managed for each project. I propose setting a policy of managing project credentials under an API project with a name equal to the verbose name of the project and an ID equal to the GitHub repository slug. For instance, the WWIC service account would live under a project named Who Was In Command with the ID sfm-cms.
We don't necessarily need to retroactively apply this policy to existing projects, because I think it might involve regenerating credentials, which would be annoying, but it does look like there are at least a few projects that have no name (My Project) and some others that I have no idea what they're for. Let's go in and give the projects descriptive names, removing any that are no longer in use.
Documentation request
We've mostly standardized on naming any / all project resources after the GitHub repository, but Google APIs projects remain a Wild West, which makes it hard to keep track of where relevant credentials are managed for each project. I propose setting a policy of managing project credentials under an API project with a name equal to the verbose name of the project and an ID equal to the GitHub repository slug. For instance, the WWIC service account would live under a project named
Who Was In Commandwith the IDsfm-cms.We don't necessarily need to retroactively apply this policy to existing projects, because I think it might involve regenerating credentials, which would be annoying, but it does look like there are at least a few projects that have no name (
My Project) and some others that I have no idea what they're for. Let's go in and give the projects descriptive names, removing any that are no longer in use.Expansion of #64, connects #170.