Load Google Cloud Pipeline Components data to DuckDB

Google Cloud Pipeline Components provides a set of prebuilt Kubeflow Pipelines components for defining and running machine learning pipelines on Google Cloud Vertex AI Pipelines and other conformant backends. Everything needed to build a working Google Cloud Pipeline Components → DuckDB pipeline is on this page: the API's base URL, authentication, endpoints, pagination and incremental field — plus a prompt that hands the whole job to your coding agent.

---

Build your Google Cloud Pipeline Components to DuckDB pipeline

Paste this prompt into Claude, Codex, or Cursor. The agent does the rest.

PromptCopy prompt
Run uvx dlthub-init@latest to build a pipeline from Google Cloud Pipeline Components to DuckDB and run it on dltHub

That scaffolds a dltHub workspace and installs the dltHub AI harness — the project rules, the secrets-management skill, and the dlt MCP server your agent needs to work safely. From there it reads the Google Cloud Pipeline Components API, proposes the endpoints to load, then writes, runs and validates the pipeline while you review rather than type. Credentials are inspected through MCP tools, so your agent never reads secrets.toml itself. How the LLM-native workflow works →

Prefer to write it yourself? Every fact the agent uses is below.

---

Google Cloud Pipeline Components API at a glance

These values come from the Google Cloud Pipeline Components API reference — the authoritative source if anything here looks out of date.

---

How do I authenticate with the Google Cloud Pipeline Components API?

Authentication is handled via standard Google Cloud authentication mechanisms, typically requiring an authenticated GCP account with the Vertex AI API enabled.

1. Get your credentials

To obtain credentials for Google Cloud APIs (such as those used by Google Cloud Pipeline Components/Vertex AI), you generally use OAuth 2.0 rather than static API keys for authenticated data operations. 1. Go to the Google Cloud Console (console.cloud.google.com). 2. Navigate to 'APIs & Services' > 'Credentials'. 3. Click 'Create Credentials' and select 'Service account'. 4. Follow the prompts to create the account, assign the 'Vertex AI User' or 'Vertex AI Administrator' role, and generate a JSON key file. 5. Alternatively, for local development, use the Google Cloud CLI (gcloud auth application-default login) to set up Application Default Credentials (ADC). For REST calls, use 'gcloud auth print-access-token' to generate a temporary bearer token.

2. Add them to .dlt/secrets.toml

Copy
[sources.google_cloud_pipeline_components_source]
access_token = "YOUR_BEARER_TOKEN_HERE"
# Alternatively, if using ADC (Application Default Credentials)
# The library will typically automatically detect the service account path
# google_application_credentials = "/path/to/your/service-account-key.json"

dlt reads this file automatically at runtime. With the harness, the setup-secrets skill prompts you for the values and never handles the raw credential in chat. For production, see setting up credentials with dlt.

---

What Google Cloud Pipeline Components data can I load into DuckDB?

These are the Google Cloud Pipeline Components endpoints dlt can load into DuckDB:

---

How do I load only new Google Cloud Pipeline Components records?

The Google Cloud Pipeline Components API reference does not document a timestamp or sequence field for these endpoints, so there is nothing to advertise here as verified. Pick a field from the endpoints table above that increases with every write, then set it as the cursor_path.

Copy
{"name": "custom_jobs", "endpoint": {
    "path": "v1/custom_job",
    # Replace with a field that increases on every write.
    "incremental": {"cursor_path": "REPLACE_ME", "initial_value": "2024-01-01T00:00:00Z"},
}}

On the first run dlt loads everything from initial_value; on every run after that it requests only what changed and appends with write_disposition="merge" if you set a primary key. See incremental loading.

---

What does the generated Google Cloud Pipeline Components pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading models and endpoints from the Google Cloud Pipeline Components API into DuckDB:

Copy
import dlt
from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources

@dlt.source
def google_cloud_pipeline_components_source(google_application_credentials=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://google-cloud-pipeline-components.readthedocs.io/en/latest/api/index.html",
            "auth": {"type": "http_basic", "username": "REPLACE_ME", "password": google_application_credentials},
        },
        "resources": [
            {"name": "custom_jobs", "endpoint": {"path": "v1/custom_job"}},
            {"name": "dataflow_jobs", "endpoint": {"path": "v1/dataflow"}}
        ],
    }
    yield from rest_api_resources(config)


def load_google_cloud_pipeline_components_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="google_cloud_pipeline_components_pipeline",
        destination="duckdb",
        dataset_name="google_cloud_pipeline_components_data",
    )
    load_info = pipeline.run(google_cloud_pipeline_components_source())
    print(load_info)


if __name__ == "__main__":
    load_google_cloud_pipeline_components_to_duckdb()

Run it with python google_cloud_pipeline_components_pipeline.py. The agent iterates on this until it loads cleanly — you review and approve, rather than write it from scratch.

---

How do I query Google Cloud Pipeline Components data in DuckDB?

dlt creates one table per resource. Query the loaded data with Python or SQL — or ask your agent to, through the MCP server's execute_sql_query tool.

Python (pandas DataFrame):

Copy
import dlt

data = dlt.pipeline("google_cloud_pipeline_components_pipeline").dataset()
df = data.custom_jobs.df()
print(df.head())

SQL:

Copy
SELECT * FROM google_cloud_pipeline_components_data.custom_jobs LIMIT 10;

See querying your data with dataset and exploring it in marimo notebooks.

---

How do I deploy the Google Cloud Pipeline Components to DuckDB pipeline in production?

The pipeline runs locally, which is ideal for prototyping and one-off analysis. When you need it on a schedule, monitored on every load, and shared with your team, deploy the same dlt code on the dltHub platform — no infrastructure to maintain. The prompt above already ends with "run it on dltHub", so your agent can take it there directly.

• Deploy & schedule — run the pipeline as a managed job with automatic retries.
• Monitor — observable job queues, alerting, and load metrics for every run.
• Transform — promote raw Google Cloud Pipeline Components loads into governed, documented models.
• Visualize & share — explore data in notebooks and publish live dashboards instead of static screenshots.

Book a demo →

---

What other destinations can I load Google Cloud Pipeline Components data to?

dlt loads into any of these — only the destination argument changes:

Set dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. On the dltHub platform the same pipeline runs against a managed Iceberg lakehouse. See the full destinations list.

---

Next steps

• Ready for production? Book a demo of the dltHub platform →
• dlt LLM-native workflow docs
• REST API source reference
• Join the dlt community on Slack