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 e05c987 Regen for commit c3d3e97d149c3db34fcfc9e0ce2bf4532ad6f0f6
add 99af69b CAMEL-17007: fix getAlias operation in camel-aws2-lambda
add 26b52fa Regen for commit 99af69b6fed1799e61bc53a3d1969654dc4d6744
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 (e05c987)
\
N -- N -- N refs/heads/regen_bot (26b52fa)
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:
.../component/aws2/lambda/Lambda2Producer.java | 1 +
.../lambda/integration/LambdaCreateGetAliasIT.java | 84 ++++++++++++++++++++++
2 files changed, 85 insertions(+)
create mode 100644
components/camel-aws/camel-aws2-lambda/src/test/java/org/apache/camel/component/aws2/lambda/integration/LambdaCreateGetAliasIT.java
