potiuk commented on a change in pull request #12466:
URL: https://github.com/apache/airflow/pull/12466#discussion_r526704452
##########
File path: airflow/provider.yaml.schema.json
##########
@@ -17,6 +17,11 @@
"type": "string"
}
},
+ "provider-package": {
Review comment:
I will also split this into two PRs - one adding "provider-package" and
one adding connections, to keep it separate.
Also after looking at how fast and easy it is to extract all the "provider"
features (extra links, connections etc.) and keep in the provider.yaml, I
think maybe even should bring the discussion about conventions for 3rd-party
providers to the devllst? This was non-goal for AIP-8 and Airflow 2.0, but it
seems we are SOOOO close to it that it's worth doing the extra effort and
discuss and vote the 3rd-party provider conventions showing examples from our
existing providers.
The nice thing about it that we can provide some examples and clear
instructions on "how to add a new 3rrd-party provider" and even a way to
generate really nice documentation with examples. Seems that we already pretty
much have what we need for that very soon, it just needs agreement on the
devlist and we still have time to discuss it before 2.0.
WDYT?
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
