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
discard 2b07e01cdc Revert "Improve health checks in example docker-compose and
clarify usage (#29408)"
add 6c13f04365 AWS Glue job hook: Make s3_bucket parameter optional
(#29659)
add ab54df3039 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 (2b07e01cdc)
\
N -- N -- N
refs/heads/revert-29408-docker-compose-change-example (ab54df3039)
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/amazon/aws/hooks/glue.py | 15 ++++-----
tests/providers/amazon/aws/hooks/test_glue.py | 48 +++++++++++++++++++++++++++
2 files changed, 54 insertions(+), 9 deletions(-)
