Status Update
No update yet.
Comments
se...@google.com
Hello,
Thank you for reaching out. I'm going to create an internal feature request. Please keep in mind that this feature request has to be analyzed and considered by the product team and I can't provide you ETA for it to be delivered. However, you can keep track of the status by following this thread.
pa...@epidemicsound.com
So a naming convention could contain:
- prefix identifier for your company
- then a name denoting describing the project
- geographical identifier (eu/us/asia)
- environment (dev/prod/test)
- suffix of 4 (or more) characters. A practice we adopted with Terraform for handling that deleted project ids in GCP cannot be reused for 30 days
So putting it together in this example string:
company-a-purpose-env-geo-1234
which is 30 characters long. Not putting too much into this convention and already at the character limit.
In our case the discussion came up because we use the same prefix for buckets and project ids (both in global namespaces). Since buckets have a higher limit (60 chars) we don't have that problem there. For consistency it would be great to be able to use the same prefix across without too much naming acrobatics.
Thank you!
se...@google.com
Thank you. I'm going to create an internal feature request. Please keep in mind that this feature request has to be analyzed and considered by the product team and I can't provide you ETA for it to be delivered. However, you can keep track of the status by following this thread.
pa...@epidemicsound.com
That is alright, thank you for considering this!
sh...@google.com
Adding to this feature request, IHAC (Mandiant) who are also requesting the increase in Project ID field from the current limit of 30 to 50 to fulfill their nomenclature rules for projects.
je...@google.com
Looks like this hasn't been touched in a while - are there any updates / plans to increase the project ID character limitation? (Customer request...)
ma...@google.com
One of our valuable customers reaches out related to this request.
This is the business impact:
>>> We have tagging and naming standards which helps us with cross charging
and billing other depts and divisions using GCP Projects. That's one of the
main reasons plus it aids us in troubleshooting and narrowing down which
dept or group or area owns it and trying to adopt a similar IaC build-out
using these standards which currently AWS has a 128 character limit which
serves our needs easily.
I believe this can be implemented in a feature because other customers might get the same request or need this kind of project name description.
Regards.
Description
As the documentation [1] states the project ID cannot be longer than 30 characters. Considering that the project ids must be globally unique some identifiers are naturally needed to ensure your project ids don't collide.
Any naming scheme or convention we adopt would most likely add some reoccurring parts (e.g environment, geography, team name) to the project ID and that quickly leads to the 30 character limit becoming quite constrictive.
I simply wish for a higher character limit :)
[1] -https://cloud.google.com/resource-manager/docs/creating-managing-projects