Add task timeout support.

[t0momi219]

Description

In Airflow, both DAGs and tasks can have timeout specified. Since dbt models likely have varying expected execution times for each layer, there could be cases where users want to apply timeout individually to each node.

How about having Cosmos retrieve timeout from the node metadata and apply them individually when rendering nodes?

Specifically, the expected time is specified in the model's config, which will be read accordingly.

version: 2
models:
  - name: stg_customers
    config:
      cosmos_task_timeout: 600 # Specify in seconds.

Related Issue(s)

closes #1316

Breaking Change?

Checklist

• I have made corresponding changes to the documentation (if required)
• I have added tests that prove my fix is effective or that my feature works

[pankajkoti]

Good idea. Can we show an example of this in one of the DAGs and potentially also mention about it somewhere in our docs?

[t0momi219]

Hi @pankajkoti ,
This PR is ready for review. Could you please check this?

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.02%. Comparing base (06f242a) to head (0621277).
Report is 15 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1317   +/-   ##
=======================================
  Coverage   96.02%   96.02%           
=======================================
  Files          67       67           
  Lines        4025     4028    +3     
=======================================
+ Hits         3865     3868    +3     
  Misses        160      160           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[pankajkoti]

LGTM. some minor suggestion inline. Thanks for dropping the SLA piece. Could you please also update the PR title & description to drop SLA & additionally reflect the renamed config key cosmos_task_timeout?

We could merge this once these minor changes are addressed & meantime hopefully @tatiana and/or @pankajastro could also get a chance to review this PR.

[tatiana]

I believe the interface for this task will change depending on the outcomes of the discussion we're having in #1339

[tatiana]

Thank you very much for the contribution, @t0momi219 ! Since #1339 has a more generic implementation, it supports the same behaviour but by using a more extensible interface:

version: 2

models:
  - name: name
    description: description
    meta:
      cosmos:
        operator_kwargs:
          execution_timeout: abcd

Therefore, I'm closing this PR.