airflow.contrib.hooks.gcp_api_base_hook
¶
Module Contents¶
-
airflow.contrib.hooks.gcp_api_base_hook.
_DEFAULT_SCOPES
= ['https://www.googleapis.com/auth/cloud-platform'][source]¶
-
airflow.contrib.hooks.gcp_api_base_hook.
_G_APP_CRED_ENV_VAR
= GOOGLE_APPLICATION_CREDENTIALS[source]¶
-
class
airflow.contrib.hooks.gcp_api_base_hook.
GoogleCloudBaseHook
(gcp_conn_id='google_cloud_default', delegate_to=None)[source]¶ Bases:
airflow.hooks.base_hook.BaseHook
A base hook for Google cloud-related hooks. Google cloud has a shared REST API client that is built in the same way no matter which service you use. This class helps construct and authorize the credentials needed to then call googleapiclient.discovery.build() to actually discover and build a client for a Google cloud service.
The class also contains some miscellaneous helper functions.
All hook derived from this base hook use the ‘Google Cloud Platform’ connection type. Three ways of authentication are supported:
Default credentials: Only the ‘Project Id’ is required. You’ll need to have set up default credentials, such as by the
GOOGLE_APPLICATION_DEFAULT
environment variable or from the metadata server on Google Compute Engine.JSON key file: Specify ‘Project Id’, ‘Keyfile Path’ and ‘Scope’.
Legacy P12 key files are not supported.
JSON data provided in the UI: Specify ‘Keyfile JSON’.
Returns an authorized HTTP object to be used to build a Google cloud service hook connection.
-
_get_field
(self, f, default=None)[source]¶ Fetches a field from extras, and returns it. This is some Airflow magic. The google_cloud_platform hook type adds custom UI elements to the hook page, which allow admins to specify service_account, key_path, etc. They get formatted as shown below.
-
static
catch_http_exception
(func)[source]¶ Function decorator that intercepts HTTP Errors and raises AirflowException with more informative message.
-
static
fallback_to_default_project_id
(func)[source]¶ Decorator that provides fallback for Google Cloud Platform project id. If the project is None it will be replaced with the project_id from the service account the Hook is authenticated with. Project id can be specified either via project_id kwarg or via first parameter in positional args.
- Parameters
func – function to wrap
- Returns
result of the function call