You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In this PUDL terraform PR we discussed renaming the pudl usage metric archive bucket. We merged the PR to not disrupt the work in #163.
I think we should rename the bucket from pudl-usage-metrics-archive.catalyst.coop to usage-metrics-archive.catalyst.coop. We should keep the archive component because if we move to Big Query for our usage metrics database we might want to have a bucket of parquet file created by the ETL. We'd probably name the bucket something like usage-metrics.catalyst.coop or usage-metrics-outputs.catalyst.coop. We can remove the pudl component because the bucket lives in the pudl-catalyst-cooperative project so all the resources should be related to pudl anyways.
I think it would be helpful to create a simple naming convention for GCP and terraform resources for consistency sake and to minimize naming discussions each time a resource is created.
The text was updated successfully, but these errors were encountered:
In this PUDL terraform PR we discussed renaming the pudl usage metric archive bucket. We merged the PR to not disrupt the work in #163.
I think we should rename the bucket from
pudl-usage-metrics-archive.catalyst.coop
tousage-metrics-archive.catalyst.coop
. We should keep thearchive
component because if we move to Big Query for our usage metrics database we might want to have a bucket of parquet file created by the ETL. We'd probably name the bucket something likeusage-metrics.catalyst.coop
orusage-metrics-outputs.catalyst.coop
. We can remove thepudl
component because the bucket lives in thepudl-catalyst-cooperative
project so all the resources should be related topudl
anyways.I think it would be helpful to create a simple naming convention for GCP and terraform resources for consistency sake and to minimize naming discussions each time a resource is created.
The text was updated successfully, but these errors were encountered: