Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Should we rename our GCP project? #74

Closed
ian-r-rose opened this issue Apr 13, 2023 · 1 comment
Closed

Should we rename our GCP project? #74

ian-r-rose opened this issue Apr 13, 2023 · 1 comment

Comments

@ian-r-rose
Copy link
Member

We currently have a "prod" GCP project for our CalInnovate called dse-product-analytics-prd-bqd.

This doesn't really adhere to our naming conventions, both before and after #60: it has a resource-type suffix of bqd, for "BigQuery Dataset". But it's not a BigQuery dataset, it's a GCP project.
A naming-convention-consistent project name would drop the resource type: dse-product-analytics-prd.

Unfortunately, it's not possible to rename a GCP project, so we'd have to create a new one and migrate resources over to it. This makes it a somewhat painful proposition.

cc @jasonlally and @britt-allen discussion
@britt-allen britt-allen self-assigned this Apr 14, 2023
@britt-allen britt-allen removed their assignment May 26, 2023
This was referenced Nov 14, 2024
Closed
Open
@ram-kishore-odi
Copy link
Contributor

ram-kishore-odi commented Dec 7, 2024 •
edited
Loading

Closing this as not planned. We are currently not focussed on GCP offerings. Please refer to this ticket for additional information - #378

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@ian-r-rose @britt-allen @ram-kishore-odi