Open fmichaelobrien opened 2 years ago
First pass at this was done in the following Gatekeeper Policy https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/blob/main/solutions/landing-zone/environments/common/general-policies/naming-rules/constraint.yaml .
Link with work in https://github.com/GoogleCloudPlatform/pbmm-on-gcp-onboarding/issues/132 Adding to architecture docs in https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/blob/dev/solutions/landing-zone/architecture.md#naming-standard https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/blob/dev/solutions/landing-zone/architecture.md#di-09-naming-standard
Is your feature request related to a problem? Please describe. Expand and define the naming standard across all the GCP components in use in the LZ
Describe the solution you'd like A clear and concise description of what you want to happen.
Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.
Additional context
DI-09: Naming Standard
Discussion
The current naming standard in the PBMM LZ keys off the constraints in https://cloud.google.com/resource-manager/docs/creating-managing-projects
We have multiple optional dept/domain/org id;s throughout (org)-(domain)-(env = prod/stg..)-vpc
see ongoing TF naming standard discussion we are bring over here in https://github.com/GoogleCloudPlatform/pbmm-on-gcp-onboarding/issues/132
Pros/Cons
Decision