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

github-bot pushed a change to branch regen_bot
in repository https://gitbox.apache.org/repos/asf/camel.git


    omit 1a454554f9f Regen for commit c3299137d5844edb69c9a4342caaf173f7f5830c
     add 20fedc05b56 camel-aws - Add dev console for AWS secrets
     add 8e932e618d7 camel-aws - Add dev console for AWS secrets
     add d43c3044a21 Regen for commit 8e932e618d7801416d2c7856db2381a52fe7129a

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   (1a454554f9f)
            \
             N -- N -- N   refs/heads/regen_bot (d43c3044a21)

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:
 .../aws/secretsmanager/SecretsDevConsole.java      | 54 ++++++++++++++++++++--
 .../vault/CloudTrailReloadTriggerTask.java         |  9 ++++
 2 files changed, 58 insertions(+), 5 deletions(-)

Reply via email to