This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a change to branch fix/CAMEL-25180
in repository https://gitbox.apache.org/repos/asf/camel.git
discard 5532c1e4b979 CAMEL-25180: camel-jbang - camel overview and camel
validate share one set of route/endpoint rules
add 641dae5e058d CAMEL-25552: camel-hashicorp-vault - the properties
function no longer shares the secret engine between lookups (#27679)
add acd2282e72fa CAMEL-25180: camel-jbang - camel overview and camel
validate share one set of route/endpoint rules
add 4cd509f6cef9 CAMEL-25180: the upgrade note quotes {{name}} literally,
and the grouping of the dynamic uri check is written out
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 (5532c1e4b979)
\
N -- N -- N refs/heads/fix/CAMEL-25180 (4cd509f6cef9)
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:
.../catalog/docs/hashicorp-vault-component.adoc | 12 +-
.../src/main/docs/hashicorp-vault-component.adoc | 12 +-
.../vault/HashicorpVaultPropertiesFunction.java | 50 ++++--
.../HashicorpVaultPropertiesFunctionTest.java | 184 +++++++++++++++++++++
.../vault/HashicorpVaultReloadTriggerTaskTest.java | 2 +-
.../ROOT/pages/camel-4x-upgrade-guide-4_24.adoc | 17 +-
.../core/commands/ai/EndpointConsumerChecks.java | 2 +-
7 files changed, 252 insertions(+), 27 deletions(-)
create mode 100644
components/camel-hashicorp-vault/src/test/java/org/apache/camel/component/hashicorp/vault/HashicorpVaultPropertiesFunctionTest.java
