This is an automated email from the ASF dual-hosted git repository.
ramackri pushed a change to branch RANGER-ozone-action-policy-feature-flag
in repository https://gitbox.apache.org/repos/asf/ranger.git
discard 75df8fdc3 RANGER-5628: Preserve Ozone audit access field when action
flag is off
discard f29e7e384 RANGER-5628: Fix checkstyle FinalParameters on changed ozone
code
discard d11b43e58 RANGER-5628: Apply access modifiers and single-line
formatting
discard 22151cdb0 RANGER-5628: Remove docker test scripts and revert
smoke-only docker config
discard 82649e7c0 RANGER-5628: Add Ozone action-policy feature flag testing
docs and scripts
discard 6c34ac95d RANGER-5628: Gate Ozone action-matches policy behind feature
flags
add b0f263ef8 RANGER-5628: Gate Ozone action-matches policy behind feature
flags
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 (75df8fdc3)
\
N -- N -- N refs/heads/RANGER-ozone-action-policy-feature-flag
(b0f263ef8)
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:
