This is an automated email from the ASF dual-hosted git repository.
taragolis pushed a change to branch revert-29408-docker-compose-change-example
in repository https://gitbox.apache.org/repos/asf/airflow.git
omit 793be818fc Revert "Improve health checks in example docker-compose and
clarify usage (#29408)"
add e6d3176082 Add `DbtCloudJobRunAsyncSensor` (#29695)
add 026f59708d Revert "Improve health checks in example docker-compose and
clarify usage (#29408)"
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (793be818fc)
\
N -- N -- N
refs/heads/revert-29408-docker-compose-change-example (026f59708d)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
airflow/providers/dbt/cloud/sensors/dbt.py | 61 ++++-
.../operators.rst | 16 ++
.../providers/dbt/cloud/sensors/test_dbt_cloud.py | 61 ++++-
.../providers/dbt/cloud/triggers}/__init__.py | 0
.../providers/dbt/cloud/triggers/test_dbt_cloud.py | 304 +++++++++++++++++++++
.../providers/dbt/cloud/example_dbt_cloud.py | 9 +-
6 files changed, 447 insertions(+), 4 deletions(-)
copy {airflow/api_connexion => tests/providers/dbt/cloud/triggers}/__init__.py
(100%)
create mode 100644 tests/providers/dbt/cloud/triggers/test_dbt_cloud.py
