[databricks-zerobus-ingest] Region tables omit GCP entirely (and are stale for AWS/Azure) — agents conclude "Zerobus is not available on GCP"

Open Beginner friendly
#264 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
Half a day
Newbie friendliness
82/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
aws, azure, gcp
Domain
documentation

Research direction

Review skills/databricks-zerobus-ingest/references/1-setup-and-authentication.md, references/5-operations-and-limits.md, and SKILL.md, then compare their region guidance with the three linked Databricks availability pages. Update the affected guidance so GCP and current AWS/Azure availability are represented, and ensure the endpoint and troubleshooting references point to authoritative information. Done means all three files no longer imply Zerobus is unavailable on GCP.

Written by the indexing model from the issue text.

Description

Problem or opportunity

The databricks-zerobus-ingest skill ships static "supported regions" tables that list only AWS and Azure:

  • skills/databricks-zerobus-ingest/references/5-operations-and-limits.md — "Regional Availability": ### AWS Supported Regions (9 regions) and ### Azure Supported Regions (11 regions); no GCP section.
  • skills/databricks-zerobus-ingest/references/1-setup-and-authentication.md — "Supported Regions" (same two clouds) and the endpoint-format table, which has rows for AWS and Azure only.

Current Databricks docs say otherwise:

Impact: an agent that follows the skill (which its troubleshooting table points to: "Region not supported → check supported regions in references/5-operations-and-limits.md") reads the absence of a GCP section as "not supported on GCP". In our case this went into a decision-grade evaluation as "Zerobus is not available on GCP; use a file-based path for GCP partners" and was only caught by a human checking the docs. Observed with plugin version 0.2.14; main (v0.2.16) still has the same tables.

Proposed change

  1. Replace the hard-coded region tables in both reference files with a pointer to the per-cloud "Ingestion availability" tables (the three URLs above), or keep the tables but add a GCP section and a "last verified" date plus the same pointer.
  2. Add the GCP row to the endpoint-format table in 1-setup-and-authentication.md.
  3. Make the SKILL.md troubleshooting entry ("Region not supported") point to the docs page rather than the static table.

Affected skill or area

skills/databricks-zerobus-ingest (references/1-setup-and-authentication.md, references/5-operations-and-limits.md, SKILL.md troubleshooting table).

Additional context

Region lists were checked against the three docs pages on 2026-09-11. No customer data or identifiers involved.

Dominant language
Python
Stars
323
Forks
82
Avg merge
50m
Merged PRs (30d)
8

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from databricks/databricks-agent-skills

All issues in databricks/databricks-agent-skills

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.