JiriOndrusek opened a new issue, #8884:
URL: https://github.com/apache/camel-quarkus/issues/8884
## Description
The `cyberark-vault` integration tests currently cover basic
`createSecret`/`getSecret` operations and unauthorized access (403), but are
missing coverage for several important component features.
## Missing Coverage
1. **Property placeholder resolution** (`{{cyberark:...}}`) — The most
common way users consume vault secrets in Camel. Requires
`camel.vault.cyberark.*` configuration and exercising
`PropertiesComponent.resolveProperty("cyberark:...")`. Other vault extensions
(HashiCorp, AWS, Azure, GCP) all test this.
2. **Dynamic secretId via message header** — All existing routes hardcode
`secretId` in the URI. The component supports
`CyberArkVaultConstants.SECRET_ID` as a message header for dynamic secret
selection, which exercises a different code path.
3. **Secret version retrieval** — `CyberArkVaultConstants.SECRET_VERSION`
header is supported but not tested. Important to verify in native mode where
reflection-based header processing could fail.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
