Copilot commented on code in PR #53362: URL: https://github.com/apache/airflow/pull/53362#discussion_r2206670398
########## providers-summary-docs/howto/create-custom-providers.rst: ########## @@ -61,83 +61,74 @@ Displaying package information in CLI/API: Exposing customized functionality to the Airflow's core: -* ``extra-links`` - this field should contain the list of all the operator class names that are adding extra links - capability. See :doc:`apache-airflow:howto/define-extra-link` for description of how to add extra link - capability to the operators of yours. +* ``auth-backends`` - this field should contain the list of all the auth backend class names that the + provider provides. See :doc:`apache-airflow:core-concepts/auth-manager/index` for description of authentication. + +* ``auth-managers`` - this field should contain the list of all the auth manager class names that the + provider provides. See :doc:`apache-airflow:core-concepts/auth-manager/index` for description of the auth managers. + +* ``bundles`` - this field should contain the list of all the bundle class names that the + provider provides. + +* ``config`` - this field should contain dictionary that should conform to the + ``airflow/config_templates/config.yml.schema.json`` with configuration contributed by the providers + See :doc:`apache-airflow:howto/set-config` for details about setting configuration. * ``connection-types`` - this field should contain the list of all the connection types together with hook class names implementing those custom connection types (providing custom extra fields and custom field behaviour). This field is available as of Airflow 2.2.0 and it replaces deprecated ``hook-class-names``. See :doc:`apache-airflow:howto/connection` for more details. -* ``secret-backends`` - this field should contain the list of all the secret backends class names that the - provider provides. See :doc:`apache-airflow:security/secrets/secrets-backend/index` for description of how - to add. - -* ``task-decorators`` - this field should contain the list of dictionaries of name/path where the decorators - are available. See :doc:`apache-airflow:howto/create-custom-decorator` for description of how to add - custom decorators. - -* ``logging`` - this field should contain the list of all the logging handler class names that the - provider provides. See :doc:`apache-airflow:administration-and-deployment/logging-monitoring/logging-tasks` - for description of the logging handlers. - -* ``notifications`` - this field should contain the notification classes. - See :doc:`apache-airflow:howto/notifications` for description of the notifications. - * ``executors`` - this field should contain the executor class names. See :doc:`apache-airflow:core-concepts/executor/index` for description of the executors. -* ``config`` - this field should contain dictionary that should conform to the - ``airflow/config_templates/config.yml.schema.json`` with configuration contributed by the providers - See :doc:`apache-airflow:howto/set-config` for details about setting configuration. - -.. TODO (potiuk): derive those descriptions directly from the schema definition +* ``extra-links`` - this field should contain the list of all the operator class names that are adding extra links + capability. See :doc:`apache-airflow:howto/define-extra-link` for description of how to add extra link + capability to the operators of yours. * ``filesystems`` - this field should contain the list of all the filesystem module names. See :doc:`apache-airflow:core-concepts/objectstorage` for description of the filesystems. +* ``hooks`` - this field should contain the list of all the hook class names that the provider provides. + See :doc:`apache-airflow:howto/connection` for description of the hooks and connections they provide. + * ``integrations`` - provides list of integrations that are available in the provider. -* ``transfers`` - this field should contain the list of all the transfer operator class names that the - provider provides. See :doc:`apache-airflow:core-concepts/operators` for description of the operators (transfers being one of the operator types). +* ``logging`` - this field should contain the list of all the logging handler class names that the + provider provides. See :doc:`apache-airflow:administration-and-deployment/logging-monitoring/logging-tasks` + for description of the logging handlers. + +* ``notifications`` - this field should contain the list of all the notification class names that the Review Comment: [nitpick] The description for notifications field is inconsistent. Line 101 says 'notification class names' while the original version mentioned just 'notification classes'. Consider using consistent terminology throughout the documentation. ```suggestion * ``notifications`` - this field should contain the list of all the notification classes that the ``` -- 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]
