Publisher
cloudquery
Repository
github.comLatest version
v1.3.6
Type
Policy
Published
Category
Cloud Infrastructure
Loading addon documentation
Publisher
cloudquery
Repository
github.comLatest version
v1.3.6
Type
Policy
Published
Category
Cloud Infrastructure
Loading addon documentation
We use tracking cookies to understand how you use the product and help us improve it. Please accept cookies to help us improve. You can always opt out later via the link in the footer.
select project_id, count(*)
from gcp_resources
group by project_id
order by count(*) desc
select project_id, region, count(*)
from gcp_resources
group by project_id, region
order by count(*) desc
_cq_id
_cq_source_name
_cq_sync_time
project_id
id
region
name
description
_cq_table
dbt
:pip install dbt-postgres
mkdir -p ~/.dbt
profiles.yml
file in your profile directory (e.g. ~/.dbt/profiles.yml
):gcp_asset_inventory: # This should match the name in your dbt_project.yml
target: dev
outputs:
dev:
type: postgres
host: 127.0.0.1
user: postgres
pass: pass
port: 5432
dbname: postgres
schema: public # default schema where dbt will build the models
threads: 1 # number of threads to use when running in parallel
profiles.yml
, you should test the connection to ensure everything is configured correctly:dbt debug
cloudquery login
in your terminal
kind: source
spec:
name: "gcp" # The source type, in this case, GCP.
path: "cloudquery/gcp" # The plugin path for handling GCP sources.
registry: "cloudquery" # The registry from which the GCP plugin is sourced.
version: "v12.3.2" # The version of the GCP plugin.
tables: ["gcp_storage_buckets"] # Include any tables that meet your requirements, separated by commas
destinations: ["postgresql"] # The destination for the data, in this case, PostgreSQL.
spec:
# GCP Spec
project_ids: ["my-project"] # The name of the GCP project you are working in
---
kind: destination
spec:
name: "postgresql" # The type of destination, in this case, PostgreSQL.
path: "cloudquery/postgresql" # The plugin path for handling PostgreSQL as a destination.
registry: "cloudquery" # The registry from which the PostgreSQL plugin is sourced.
version: "v8.0.1" # The version of the PostgreSQL plugin.
spec:
connection_string: "${POSTGRESQL_CONNECTION_STRING}" # set the environment variable in a format like
# postgresql://postgres:pass@localhost:5432/postgres?sslmode=disable
# You can also specify the connection string in DSN format, which allows for special characters in the password:
# connection_string: "user=postgres password=pass+0-[word host=localhost port=5432 dbname=postgres"
dbt_project.yml
resides.dbt run
command, it might be useful to check for any potential issues:dbt compile
dbt run
dbt
models and create tables/views in your destination database as defined in your models.dbt-core
and not dbt-cloud-cli
as dbt-core does not require extra authentication.dbt run
commands can be used:dbt run --select +<model_name>
dbt run --models +<model_name>