This is an automated email from the ASF dual-hosted git repository.

ephraimbuddy pushed a change to branch dag-processor-publication-api
in repository https://gitbox.apache.org/repos/asf/airflow.git


 discard 0f0dcf59d4f Allow Dag processors to publish metadata through the 
Execution API
 discard 2fbb3eeb483 Keep Dag parsing results aligned with refreshed bundle 
sources
     add 6bb9d0c0d01 Distinguish invalid Dag access control from FAB backend 
failures
     add 722db9c78c2 Keep Dag parsing results aligned with refreshed bundle 
sources
     add a769ccc99b9 Allow Dag processors to publish metadata through the 
Execution API

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   (0f0dcf59d4f)
            \
             N -- N -- N   refs/heads/dag-processor-publication-api 
(a769ccc99b9)

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:
 .../fab/auth_manager/security_manager/override.py  | 10 ++++--
 .../tests/unit/fab/auth_manager/test_security.py   | 39 ++++++++++++----------
 2 files changed, 29 insertions(+), 20 deletions(-)

Reply via email to