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-kamelets.git.
omit 18e47bb Regen for commit 526fbf85928ebd5e288fc669c41a13bb2ed60d53
add 02702fe Regen for commit 526fbf85928ebd5e288fc669c41a13bb2ed60d53
add 782fa1d AWS S3 Streaming upload: set the example batch size as a
string
add 63d8a4e AWS S3 Streaming upload: set the example batch size as a
string
add a534a06 Log Sink Kamelet: Added Kamelet group
add f9c62ba Log Sink Kamelet: Added Kamelet group
add b01ac1e Regen docs
add b8e147b Regen docs
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 (18e47bb)
\
N -- N -- N refs/heads/regen_bot (b8e147b)
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-s3-streaming-upload-sink.kamelet.yaml | 2 +-
.../ROOT/assets/images/kamelets/log-sink.svg | 41 ++++++++++++++++++++
docs/modules/ROOT/nav.adoc | 1 +
.../ROOT/pages/aws-s3-streaming-upload-sink.adoc | 2 +-
.../ROOT/pages/{http-sink.adoc => log-sink.adoc} | 44 ++++++++++------------
.../aws-s3-streaming-upload-sink.kamelet.yaml | 2 +-
.../main/resources/kamelets/log-sink.kamelet.yaml | 1 +
log-sink.kamelet.yaml | 1 +
8 files changed, 67 insertions(+), 27 deletions(-)
create mode 100644 docs/modules/ROOT/assets/images/kamelets/log-sink.svg
copy docs/modules/ROOT/pages/{http-sink.adoc => log-sink.adoc} (64%)
