Standardize connection docs labels across providers#63455
Conversation
josh-fell
left a comment
There was a problem hiding this comment.
There are some other places where there are multiple connection doc tags in providers. You should also make sure any other references in any of the docs that might reference the existing labels are updated too.
Looks like a good start on a cleanup effort!
|
Also like we discussed on Slack (I think), please create a pre-commit/prek hook (or crete/update existing Sphinx extensions) to ensure it follows this convention |
|
hi @kaxil, just to confirm: the pre-commit hook should make sure that the connection-type in provider.yaml, the title anchor in the corresponding .rst documentation file, and the references to it all use the same value, right ? |
Yup |
|
hi @kaxil, ive added the prek hook which checks if the anchors and references are valid. |
|
Could you rebase on main to see if it fixes CI errors |
db3930d to
746bfba
Compare
|
CI failures: https://github.com/apache/airflow/actions/runs/23073391048/job/67029554773?pr=63455 that needs fixing |
238baef to
77d217a
Compare
77d217a to
03698e5
Compare
|
nice ! |
* Standardize connection docs labels across providers * Standardize connection docs labels across providers[2] * remove duplicates * Add pre-commit hook * executable permission * CI fixes with correct refs in python files
Tried to standardize howto/connection:{conn_type} labels in provider .rst docs to match provider.yaml connection-type values as suggested in following issue.
Closes: #63348
Was generative AI tooling used to co-author this PR?
Generated-by: Cursor/Claude following the guidelines
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.