potiuk commented on code in PR #48849:
URL: https://github.com/apache/airflow/pull/48849#discussion_r2030936301
##########
providers/airbyte/src/airflow/providers/airbyte/get_provider_info.py:
##########
@@ -26,35 +26,6 @@ def get_provider_info():
"package-name": "apache-airflow-providers-airbyte",
"name": "Airbyte",
"description": "`Airbyte <https://airbyte.com/>`__\n",
- "state": "ready",
- "source-date-epoch": 1743477757,
- "versions": [
- "5.0.1",
- "5.0.0",
- "4.0.0",
- "3.9.0",
- "3.8.1",
- "3.8.0",
- "3.7.0",
- "3.6.0",
- "3.5.1",
- "3.5.0",
- "3.4.0",
- "3.3.2",
- "3.3.1",
- "3.3.0",
- "3.2.1",
- "3.2.0",
- "3.1.0",
- "3.0.0",
- "2.1.4",
- "2.1.3",
- "2.1.2",
- "2.1.1",
- "2.1.0",
- "2.0.0",
- "1.0.0",
- ],
"integrations": [
Review Comment:
See the latest change - it's not going to succeed **yet** - but I added
quickly the missing descriptions, and will iterate with that one on automating
retrieval of the description in the providers docs - I also added a
non-breaking note in all providers that the provider-info entrypoint will now
be trimmed down to what provider_info schema describes. cc: @eladkal -> you
might want to take a look.
BTW. This is also a clear sign that our "automate everything with pre-comit"
approach makes sense - we got desynchronized quite a bit for what the provider
info had and what capabilities we added to provider (because we did not have
automation here). So I will continue to relentless automate it to keep
consistency.
BTW. Provider Info from the very beginning was supposed to be more of "I
announce my capabilities" than something we will internally use , it was more
for external use, if someone wants to build any extensions on top of airflow
having provider's information being captured and exposed this way might be
quite useful.
--
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]
