Improve discoverability of Provider packages' functionality #17775
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The ``hook-class-names`` provider's meta-data property has been deprecated and is now replaced by ``connection-types`` property. This documents the change.
|
This PR implements what we have been discussing in the devlist thread: https://lists.apache.org/x/thread.html/rf3e3beba4dac92adcd2e2f11088f992c23baa1aa43518e9efbb625f8@%3Cdev.airflow.apache.org%3E There are a number of new pages in the "apache-providers" "Core Extensions" chapter: Providers-packages main doc:
"Core Extensions" provider's page:
continued here:
Dedicated pages for each functionality - "Writing logs" example:
All those pages are inter-linked form the chapters that describe given functionality in the "apache-airflow" - for example "Writing logs" here:
|
mik-laj
reviewed
Aug 23, 2021
mik-laj
reviewed
Aug 23, 2021
The documentation of provider packages was rather disconnected from the apache-airlfow documentation. It was hard to find the ways how the apache airflow's core extensions are implemented by the community managed providers - you needed to know what you were looking for, and you could not find links to the summary of the core-functionality extended by providers when you were looking at the functionality (like logging/secret backends/connections/auth) This PR inroduces much more comprehensive cross-linking between the airflow core functionalithy and the community-managed providers that are providing extensions to the core functionality.
49b88db to
b6bbe32
Compare
mik-laj
approved these changes
Aug 23, 2021
|
The PR most likely needs to run full matrix of tests because it modifies parts of the core of Airflow. However, committers might decide to merge it quickly and take the risk. If they don't merge it quickly - please rebase it to the latest main at your convenience, or amend the last commit of the PR, and push it with --force-with-lease. |
eladkal
added a commit
to eladkal/airflow
that referenced
this pull request
Jun 28, 2022
now that providers>=2.2 there is no need for the hook-class-names any longer. refrence to apache#17775
potiuk
pushed a commit
that referenced
this pull request
Jun 28, 2022
* Remove `hook-class-names` from provider.yaml now that providers>=2.2 there is no need for the hook-class-names any longer. refrence to #17775 * fix `airflow/provider.yaml.schema.json` and `provider_info.schema.json` * undo changes in `provider_info.schema.json`
leahecole
pushed a commit
to GoogleCloudPlatform/composer-airflow
that referenced
this pull request
Jan 30, 2023
* Remove `hook-class-names` from provider.yaml now that providers>=2.2 there is no need for the hook-class-names any longer. refrence to apache/airflow#17775 * fix `airflow/provider.yaml.schema.json` and `provider_info.schema.json` * undo changes in `provider_info.schema.json` GitOrigin-RevId: 510a6bab4595cce8bd5b1447db957309d70f35d9
kosteev
pushed a commit
to GoogleCloudPlatform/composer-airflow
that referenced
this pull request
Sep 18, 2024
* Remove `hook-class-names` from provider.yaml now that providers>=2.2 there is no need for the hook-class-names any longer. refrence to apache/airflow#17775 * fix `airflow/provider.yaml.schema.json` and `provider_info.schema.json` * undo changes in `provider_info.schema.json` GitOrigin-RevId: 510a6bab4595cce8bd5b1447db957309d70f35d9
kosteev
pushed a commit
to GoogleCloudPlatform/composer-airflow
that referenced
this pull request
Nov 7, 2024
* Remove `hook-class-names` from provider.yaml now that providers>=2.2 there is no need for the hook-class-names any longer. refrence to apache/airflow#17775 * fix `airflow/provider.yaml.schema.json` and `provider_info.schema.json` * undo changes in `provider_info.schema.json` GitOrigin-RevId: 510a6bab4595cce8bd5b1447db957309d70f35d9
kosteev
pushed a commit
to GoogleCloudPlatform/composer-airflow
that referenced
this pull request
May 3, 2025
* Remove `hook-class-names` from provider.yaml now that providers>=2.2 there is no need for the hook-class-names any longer. refrence to apache/airflow#17775 * fix `airflow/provider.yaml.schema.json` and `provider_info.schema.json` * undo changes in `provider_info.schema.json` GitOrigin-RevId: 510a6bab4595cce8bd5b1447db957309d70f35d9
kosteev
pushed a commit
to GoogleCloudPlatform/composer-airflow
that referenced
this pull request
May 23, 2025
* Remove `hook-class-names` from provider.yaml now that providers>=2.2 there is no need for the hook-class-names any longer. refrence to apache/airflow#17775 * fix `airflow/provider.yaml.schema.json` and `provider_info.schema.json` * undo changes in `provider_info.schema.json` GitOrigin-RevId: 510a6bab4595cce8bd5b1447db957309d70f35d9
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The documentation of provider packages was rather disconnected
from the apache-airlfow documentation. It was hard to find the
ways how the apache airflow's core extensions are implemented by
the community managed providers - you needed to know what you were
looking for, and you could not find links to the summary of the
core-functionality extended by providers when you were looking at
the functionality (like logging/secret backends/connections/auth)
This PR inroduces much more comprehensive cross-linking between
the airflow core functionalithy and the community-managed providers
that are providing extensions to the core functionality.
Depends on #17767