We've been using it as an author. Not necessarily valid on the workers. I figure the email of a team could go in the feild that emails on failure. If you want to add a team tag for a plug-in you're working on, you might consider a specific dictionary entry in the dag/task params maybe.
On Mon, Oct 23, 2017, 7:35 PM James Freedman <[email protected]> wrote: > Hi all, > > The Airflow documentation recommends setting the owner field of a task to > the UNIX user airflow is running under, but I can't see anything in the > source code that makes use of it other than: > - run_as_owner in the Hive operator > - the notify_owner decorator for e-mail-on-DAG-action > > Is there anything critical I've missed? Or, more crucially, anything that > would break if the owner was not a valid system user? > > Our use-case is we send Datadog events (and then on to PagerDuty) on SLA > misses and I'd like to use the owner field to tag the team that owns a DAG. > > Kind regards, > James >
