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 30bed06 Regen for commit 2ba5ea35135a72759ceb4d31cbe61c00105b2ddc
add 9deb58d Camel-Azure Key Vault: Add Metadata for producerOnly
add 5798bce Camel-Azure Key Vault: Add Metadata for producerOnly
add 1fe1424 Camel-Azure Key Vault: Add Spring Boot partial
add b999789 Camel-Azure Key Vault: Add Docs about Producer operations
add cf06207 Camel-Azure Key Vault: Add Docs about Producer operations
add 2ba8dd5 Regen for commit cf0620750613b336a02a44e7b2ea55bc18570093
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 (30bed06)
\
N -- N -- N refs/heads/regen_bot (2ba8dd5)
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:
.../camel/catalog/components/azure-key-vault.json | 10 +-
.../key/vault/KeyVaultComponentConfigurer.java | 6 -
.../key/vault/KeyVaultEndpointConfigurer.java | 18 --
.../key/vault/KeyVaultEndpointUriFactory.java | 5 +-
.../component/azure/key/vault/azure-key-vault.json | 10 +-
.../src/main/docs/azure-key-vault-component.adoc | 54 +++-
.../azure/key/vault/KeyVaultEndpoint.java | 1 +
.../dsl/AzureKeyVaultComponentBuilderFactory.java | 23 --
.../src/generated/resources/metadata.json | 2 +-
.../dsl/KeyVaultEndpointBuilderFactory.java | 343 +--------------------
.../EndpointConsumerDeserializersResolver.java | 1 -
11 files changed, 71 insertions(+), 402 deletions(-)