kaxil opened a new pull request, #63349:
URL: https://github.com/apache/airflow/pull/63349
Connection "View docs" links in the registry were broken for many providers
— they all pointed to `connections/index.html` which 404s for providers like
Tableau (`connections/tableau.html`) and Google BigQuery
(`connections/bigquery.html`).
**Root cause:** Two bugs working together:
1. `extract_metadata.py` and `extract_versions.py` hardcoded
`connections/index.html` for every connection type
2. `connection-builder.js` tried to "fix" this by replacing `index.html`
with `{connType}.html` — but conn_type names don't match filenames (e.g.
`gcpbigquery` → `connections/gcpbigquery.html` which is 404; correct page is
`connections/bigquery.html`)
**Fix:** Parse each provider's Sphinx `objects.inv` inventory file to
resolve the correct per-connection-type URL:
- `std:label howto/connection:{conn_type}` entries give exact conn_type →
page mapping
- `std:doc connections/{name}` entries fill gaps
- Unresolved conn_types fall back to `connections/` (the connection listing
page)
The JS now uses the resolved URL as-is instead of mangling it.
### Examples of fixed URLs
| Provider | conn_type | Before (404) | After (200) |
|----------|-----------|-------------|-------------|
| Tableau | `tableau` | `connections/index.html` |
`connections/tableau.html` |
| Google | `gcpbigquery` | `connections/gcpbigquery.html` |
`connections/bigquery.html` |
| K8s | `kubernetes` | `connections/index.html` |
`connections/kubernetes.html` |
| Amazon | `emr` | `connections/index.html` | `connections/emr.html` |
### Remaining gaps
Some Google conn_types (`google_cloud_platform`, `gcpcloudsql`, `gcpssh`)
don't have matching `howto/connection:` labels in the Sphinx docs, so they fall
back to `connections/`. This issue
(https://github.com/apache/airflow/issues/63348) will track adding consistent
labels across all providers.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
