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 e8c4da75d Regen for commit 4b89afaef8e47d580314308a76d949ad4bfdb983
add e2ef32b04 Regen for commit 4b89afaef8e47d580314308a76d949ad4bfdb983
(#2673)
add b0790956b Add Databricks source and sink Kamelet (#2672)
add 65b0a9390 Regen for commit b0790956b189d1eb216658bf293966faf41e442a
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 (e8c4da75d)
\
N -- N -- N refs/heads/regen_bot (65b0a9390)
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:
docs/modules/ROOT/nav.adoc | 2 +
kamelets/databricks-sink.kamelet.yaml | 103 +++++++++++++++++++++
.../databricks-source.kamelet.yaml | 76 ++++++++-------
.../kamelets/databricks-sink.kamelet.yaml | 103 +++++++++++++++++++++
...kamelet.yaml => databricks-source.kamelet.yaml} | 76 ++++++++-------
5 files changed, 282 insertions(+), 78 deletions(-)
create mode 100644 kamelets/databricks-sink.kamelet.yaml
copy
library/camel-kamelets/src/main/resources/kamelets/aws-redshift-source.kamelet.yaml
=> kamelets/databricks-source.kamelet.yaml (51%)
create mode 100644
library/camel-kamelets/src/main/resources/kamelets/databricks-sink.kamelet.yaml
copy
library/camel-kamelets/src/main/resources/kamelets/{aws-redshift-source.kamelet.yaml
=> databricks-source.kamelet.yaml} (51%)
