Establishing the Connection to the Airflow Environment
The communication between the Airflow Agent and the target system is established by Connection objects. They contain the parameters (target system endpoint, login data and so on) required to authenticate on and connect to the target cloud solution. As an administrator user, you create the necessary Airflow Connection objects. As a developer or object designer, you assign the respective Airflow Connection object to the Automic Automation Run DAG Jobs to execute and monitor the jobs on the target cloud solution without leaving Automic Automation. This topic explains how to configure the Airflow Connection object.
The Airflow Agent Integration supports the following authentication methods:
-
For Apache Airflow
-
Basic
-
OAuth2
-
-
For the Google Cloud Composer
-
Service account key
-
Workload identity
-
To configure an Automic Automation Airflow Connection object you will need the authentication data (credentials, endpoints, tokens and so forth) that enable the login to the target cloud solution. You can get this data from the team in your organization that is responsible for maintaining the target cloud solution.
The Connection Object definition consists of an Agent-specific page and pages that are common to all Connection objects.
Adding an Airflow Connection Object
-
In the Automic Web Interface, go to the Process Assembly perspective. It opens to the Explorer view that contains the list of jobs that are available to you in your system.
-
You have two options:
-
Right-click anywhere on the list and select Add > Add Object.
-
Click the Add Object button on the toolbar.
-
-
On the Add Object dialog, start typing Airflow in the Search field.
-
Select AIRFLOW Connection and click Add. The Object Name dialog is displayed.
-
Enter a descriptive Name.
-
Optionally, enter a short and descriptive Title that helps you recognize the purpose of the object.
-
Click OK. A new page opens where you can start with the object definitions.
AIRFLOW Page
On this page you specify the parameters that are specific to the cloud solution that you want to connect to.
Connecting to an Apache Airflow Target
The Agent integration with Apache Airflow supports two authentication methods, Basic and OAuth2.
To Connect to an Apache Airflow Environment
-
Specify the Endpoint that identifies the environment that you want to connect to.
Example: http://<hostname>:<port>/api/v1
-
In Provider select Apache Airflow.
-
Select the Authentication Type used to authenticate to the target environment. Reach out to the team that maintains the credentials for information about them.
-
Basic
Credentials required to log in to Apache Airflow.
-
Username
The name of the user with privileges to access the Apache Airflow environment.
-
Password
Password of the Apache Airflow user.
-
-
OAuth2
-
OAuth2 Endpoint
URL that clients call to request the token.
-
Client ID
Identifier as defined in your OAuth2 system.
-
Client Secret
Encrypted secret value as defined in your OAuth2 system.
-
Scope
Range of applications that the token will grant access to.
-
-
-
Save the object.
Connecting to a Google Cloud Composer Target
The Agent integration with Apache Airflow supports two authentication types:
-
Service account key
-
Workload identity if you have an AAKE environment and both AAKE and the Agent run in a Kubernetes cluster
To Connect to an Google Cloud Composer Environment
-
In Endpoint specify the URL that identifies the network address of the Google Cloud Composer environment.
-
In Provider select Google Cloud Composer.
-
In Authentication Type select one of the following:
-
Service Account Key
In Service Account Key enter the file path to the JSON file that contains the authentication information.
When creating a service account in the Google Cloud Composer, a public key can be created which provides the JSON file. Contact the team in your organization that is responsible for maintaining the Google Cloud Composer environment as they will be able to provide you with the data that you need.
-
Workload Identity
Select this option if you have an AAKE environment and the Airflow Agent and AAKE run in a Kubernetes cluster.
With this option you do not have to enter anything else.
For more information about containerized Agents in AAKE, see Installing Containerized Java Agents in the Automic Automation documentation.
-
-
Save the object.
Common Definition Pages
In addition to the Agent-specific connection parameters, you can also specify optional properties. You do so on the following definition pages:
Next Step
As soon as the Connection object is configured, developers and object designers can select it when defining the Run DAG Jobs.
See also: