This is an automated email from the ASF dual-hosted git repository.
acosentino pushed a change to branch task-29
in repository https://gitbox.apache.org/repos/asf/camel.git
discard 093a7aa68b46 PQC docs
discard ba3c0efdffd7 CAMEL-23204 - CAMEL-PQC: Enforce key status checks before
cryptographic operations in PQCProducer
add a5f53c6dd414 chore(deps): Bump aws-java-sdk2-version from 2.42.13 to
2.42.14
add 73914b118c9c CAMEL-23203 - Camel-PQC: Add algorithm metadata to hybrid
wire formats (#22053)
add 122326505f44 CAMEL-23204 - CAMEL-PQC: Enforce key status checks before
cryptographic operations in PQCProducer
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 (093a7aa68b46)
\
N -- N -- N refs/heads/task-29 (122326505f44)
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:
.../org/apache/camel/catalog/components/pqc.json | 14 +-
components/camel-pqc/pom.xml | 5 +
.../camel-pqc/src/main/docs/pqc-component.adoc | 8 +-
.../apache/camel/component/pqc/PQCAlgorithmId.java | 150 +++++++++++++++++++++
.../component/pqc/PQCKeyStatusEnforcementTest.java | 39 +++---
.../component/dsl/PqcComponentBuilderFactory.java | 23 ++++
.../endpoint/dsl/PQCEndpointBuilderFactory.java | 40 ++++++
parent/pom.xml | 2 +-
8 files changed, 249 insertions(+), 32 deletions(-)
create mode 100644
components/camel-pqc/src/main/java/org/apache/camel/component/pqc/PQCAlgorithmId.java
