diff --git a/airflow/contrib/hooks/azure_cosmos_hook.py b/airflow/contrib/hooks/azure_cosmos_hook.py
index 01b4007b0308f..8a3cc41d51805 100644
--- a/airflow/contrib/hooks/azure_cosmos_hook.py
+++ b/airflow/contrib/hooks/azure_cosmos_hook.py
@@ -16,6 +16,14 @@
# KIND, either express or implied. See the License for the
# specific language governing permissions and limitations
# under the License.
+"""
+This module contains integration with Azure CosmosDB.
+
+AzureCosmosDBHook communicates via the Azure Cosmos library. Make sure that a
+Airflow connection of type `azure_cosmos` exists. Authorization can be done by supplying a
+login (=Endpoint uri), password (=secret key) and extra fields database_name and collection_name to specify
+the default database and collection to use (see connection `azure_cosmos_default` for an example).
+"""
import azure.cosmos.cosmos_client as cosmos_client
from azure.cosmos.errors import HTTPFailure
import uuid
diff --git a/airflow/contrib/hooks/azure_data_lake_hook.py b/airflow/contrib/hooks/azure_data_lake_hook.py
index 9eb7af7f8a71e..186cae5d1d485 100644
--- a/airflow/contrib/hooks/azure_data_lake_hook.py
+++ b/airflow/contrib/hooks/azure_data_lake_hook.py
@@ -17,7 +17,14 @@
# specific language governing permissions and limitations
# under the License.
#
-
+"""
+This module contains integration with Azure Data Lake.
+
+AzureDataLakeHook communicates via a REST API compatible with WebHDFS. Make sure that a
+Airflow connection of type `azure_data_lake` exists. Authorization can be done by supplying a
+login (=Client ID), password (=Client Secret) and extra fields tenant (Tenant) and account_name (Account Name)
+(see connection `azure_data_lake_default` for an example).
+"""
from airflow.hooks.base_hook import BaseHook
from azure.datalake.store import core, lib, multithread
diff --git a/airflow/contrib/hooks/wasb_hook.py b/airflow/contrib/hooks/wasb_hook.py
index d3a766cf69de7..077f8d92205e1 100644
--- a/airflow/contrib/hooks/wasb_hook.py
+++ b/airflow/contrib/hooks/wasb_hook.py
@@ -17,7 +17,14 @@
# specific language governing permissions and limitations
# under the License.
#
-
+"""
+This module contains integration with Azure Blob Storage.
+
+It communicate via the Window Azure Storage Blob protocol. Make sure that a
+Airflow connection of type `wasb` exists. Authorization can be done by supplying a
+login (=Storage account name) and password (=KEY), or login and SAS token in the extra
+field (see connection `wasb_default` for an example).
+"""
from airflow.exceptions import AirflowException
from airflow.hooks.base_hook import BaseHook
@@ -26,7 +33,7 @@
class WasbHook(BaseHook):
"""
- Interacts with Azure Blob Storage through the wasb:// protocol.
+ Interacts with Azure Blob Storage through the ``wasb://`` protocol.
Additional options passed in the 'extra' field of the connection will be
passed to the `BlockBlockService()` constructor. For example, authenticate
diff --git a/docs/integration.rst b/docs/integration.rst
index c093b7df72c1a..684f76ae9fa2c 100644
--- a/docs/integration.rst
+++ b/docs/integration.rst
@@ -27,9 +27,7 @@ Integration
Azure: Microsoft Azure
----------------------
-Airflow has limited support for Microsoft Azure: interfaces exist only for Azure Blob
-Storage and Azure Data Lake. Hook, Sensor and Operator for Blob Storage and
-Azure Data Lake Hook are in contrib section.
+Airflow has limited support for `Microsoft Azure `__.
Logging
'''''''
@@ -38,80 +36,78 @@ Airflow can be configured to read and write task logs in Azure Blob Storage.
See :ref:`write-logs-azure`.
-Azure Blob Storage
-''''''''''''''''''
-
-All classes communicate via the Window Azure Storage Blob protocol. Make sure that a
-Airflow connection of type `wasb` exists. Authorization can be done by supplying a
-login (=Storage account name) and password (=KEY), or login and SAS token in the extra
-field (see connection `wasb_default` for an example).
-
-The operators are defined in the following module:
-
-* :mod:`airflow.contrib.sensors.wasb_sensor`
-* :mod:`airflow.contrib.operators.wasb_delete_blob_operator`
-* :mod:`airflow.contrib.sensors.wasb_sensor`
-* :mod:`airflow.contrib.operators.file_to_wasb`
-
-They use :class:`airflow.contrib.hooks.wasb_hook.WasbHook` to communicate with Microsoft Azure.
-
-Azure File Share
-''''''''''''''''
+Operators and Hooks
+'''''''''''''''''''
-Cloud variant of a SMB file share. Make sure that a Airflow connection of
-type `wasb` exists. Authorization can be done by supplying a login (=Storage account name)
-and password (=Storage account key), or login and SAS token in the extra field
-(see connection `wasb_default` for an example).
+Service operators and hooks
+"""""""""""""""""""""""""""
-It uses :class:`airflow.contrib.hooks.azure_fileshare_hook.AzureFileShareHook` to communicate with Microsoft Azure.
+These integrations allow you to perform various operations within the Microsoft Azure.
-Azure CosmosDB
-''''''''''''''
-AzureCosmosDBHook communicates via the Azure Cosmos library. Make sure that a
-Airflow connection of type `azure_cosmos` exists. Authorization can be done by supplying a
-login (=Endpoint uri), password (=secret key) and extra fields database_name and collection_name to specify the
-default database and collection to use (see connection `azure_cosmos_default` for an example).
+.. list-table::
+ :header-rows: 1
-The operators are defined in the following modules:
+ * - Service name
+ - Hook
+ - Operators
+ - Sensors
-* :mod:`airflow.contrib.operators.azure_cosmos_operator`
-* :mod:`airflow.contrib.sensors.azure_cosmos_sensor`
+ * - `Azure Blob Storage `__
+ -
+ - :mod:`airflow.contrib.operators.wasb_delete_blob_operator`
+ - :mod:`airflow.contrib.sensors.wasb_sensor`
-They also use :class:`airflow.contrib.hooks.azure_cosmos_hook.AzureCosmosDBHook` to communicate with Microsoft Azure.
+ * - `Azure Container Instances `__
+ - :mod:`airflow.contrib.hooks.azure_container_instance_hook`,
+ :mod:`airflow.contrib.hooks.azure_container_registry_hook`,
+ :mod:`airflow.contrib.hooks.azure_container_volume_hook`
+ - :mod:`airflow.contrib.operators.azure_container_instances_operator`
+ -
-Azure Data Lake
-'''''''''''''''
+ * - `Azure Cosmos DB `__
+ - :mod:`airflow.contrib.hooks.azure_cosmos_hook`
+ - :mod:`airflow.contrib.operators.azure_cosmos_operator`
+ - :mod:`airflow.contrib.sensors.azure_cosmos_sensor`
-AzureDataLakeHook communicates via a REST API compatible with WebHDFS. Make sure that a
-Airflow connection of type `azure_data_lake` exists. Authorization can be done by supplying a
-login (=Client ID), password (=Client Secret) and extra fields tenant (Tenant) and account_name (Account Name)
-(see connection `azure_data_lake_default` for an example).
+ * - `Azure Data Lake Storage `__
+ - :mod:`airflow.contrib.hooks.azure_data_lake_hook`
+ - :mod:`airflow.contrib.operators.adls_list_operator`
+ -
-The operators are defined in the following modules:
+ * - `Azure Files `__
+ - :mod:`airflow.contrib.hooks.azure_fileshare_hook`
+ -
+ -
-* :mod:`airflow.contrib.operators.adls_list_operator`
-* :mod:`airflow.contrib.operators.adls_to_gcs`
-They also use :class:`airflow.contrib.hooks.azure_data_lake_hook.AzureDataLakeHook` to communicate with Microsoft Azure.
+Transfer operators and hooks
+""""""""""""""""""""""""""""
+These integrations allow you to copy data from/to Microsoft Azure.
-Azure Container Instances
-'''''''''''''''''''''''''
+.. list-table::
+ :header-rows: 1
-Azure Container Instances provides a method to run a docker container without having to worry
-about managing infrastructure. The AzureContainerInstanceHook requires a service principal. The
-credentials for this principal can either be defined in the extra field ``key_path``, as an
-environment variable named ``AZURE_AUTH_LOCATION``,
-or by providing a login/password and tenantId in extras.
+ * - Source
+ - Destination
+ - Guide
+ - Operators
-The operator is defined in the :mod:`airflow.contrib.operators.azure_container_instances_operator` module.
+ * - `Azure Data Lake Storage `__
+ - `Google Cloud Storage (GCS) `__
+ -
+ - :mod:`airflow.contrib.operators.adls_to_gcs`
-They also use :class:`airflow.contrib.hooks.azure_container_volume_hook.AzureContainerVolumeHook`,
-:class:`airflow.contrib.hooks.azure_container_registry_hook.AzureContainerRegistryHook` and
-:class:`airflow.contrib.hooks.azure_container_instance_hook.AzureContainerInstanceHook` to communicate with Microsoft Azure.
+ * - Local
+ - `Azure Blob Storage `__
+ -
+ - :mod:`airflow.contrib.operators.file_to_wasb`
-The AzureContainerRegistryHook requires a host/login/password to be defined in the connection.
+ * - `Oracle `__
+ - `Azure Data Lake Storage `__
+ -
+ - :mod:`airflow.contrib.operators.oracle_to_azure_data_lake_transfer`
.. _AWS:
@@ -578,7 +574,7 @@ These integrations allow you to copy data from/to Google Cloud Platform.
:ref:`[1] ` Those discovery-based operators use
:class:`airflow.gcp.hooks.discovery_api.GoogleDiscoveryApiHook` to communicate with Google
-Services via the `Google API Python Client `__.`
+Services via the `Google API Python Client `__.
Please note that this library is in maintenance mode hence it won't fully support GCP in the future.
Therefore it is recommended that you use the custom GCP Service Operators for working with the Google
Cloud Platform.
diff --git a/tests/contrib/hooks/test_azure_fileshare_hook.py b/tests/contrib/hooks/test_azure_fileshare_hook.py
index 9b7c210b7a483..c2dc8975900ba 100644
--- a/tests/contrib/hooks/test_azure_fileshare_hook.py
+++ b/tests/contrib/hooks/test_azure_fileshare_hook.py
@@ -17,7 +17,14 @@
# specific language governing permissions and limitations
# under the License.
#
-
+"""
+This module contains integration with Azure File Share.
+
+Cloud variant of a SMB file share. Make sure that a Airflow connection of
+type `wasb` exists. Authorization can be done by supplying a login (=Storage account name)
+and password (=Storage account key), or login and SAS token in the extra field
+(see connection `wasb_default` for an example).
+"""
import json
import unittest