Mailing-List: contact dev-help@airflow.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@airflow.incubator.apache.org
MIME-Version: 1.0
From: Feng Lu <fenglu@google.com.INVALID>
Date: Tue, 6 Jun 2017 15:44:20 -0700
Message-ID: <CACZXaYsGsXO2Gb9zhxamwgsfDGUyxWBfmmHi1qG=AL9JknJurQ@mail.gmail.com>
Subject: Adding airflow top-level label(s)
To: dev@airflow.incubator.apache.org
Content-Type: multipart/alternative; boundary="001a114713744ada6a0551525c6e"
archived-at: Tue, 06 Jun 2017 22:44:27 -0000

--001a114713744ada6a0551525c6e
Content-Type: text/plain; charset="UTF-8"

Hi,

Resource label/tag has gained increasing popularity, for example, both GCP
and AWS allow labels/tags to be attached to the cloud resources they
offered. I am wondering whether the airflow community is interested in
adding some default top-level airflow labels for all cloud resources that
support labeling, spawned from airflow. In other words, all operators
creating/using these resources will include the airflow labels (e.g.,
"airflow-version" : "1.8.1").

The benefits are twofold:
- enable measuring the impact of apache airflow quantitatively at different
places.
- allow users to better organize airflow triggered cloud resources.

These top-level labels will then be merged with user-provided labels
specified in the various operators (e.g.
https://github.com/apache/incubator-airflow/blob/master/airflow/contrib/operators/dataproc_operator.py#L55
).

Thanks.

Feng

--001a114713744ada6a0551525c6e--