davsclaus opened a new pull request, #27680: URL: https://github.com/apache/camel/pull/27680
Vault properties functions are single shared instances (properties can be resolved at runtime from many threads), but kept unsynchronized per-instance state. - **AWS Secrets Manager, AWS Parameter Store, Azure Key Vault, Google Secret Manager, IBM Secrets Manager, CyberArk**: the set of secrets in use (written on every lookup, read by the secret refresh tasks and dev consoles) is now a concurrent set, exposed as a read-only view. All callers in the repo only copy it. - **IBM Secrets Manager**: the secret group was an instance field set per lookup, so concurrent lookups could read another lookup's group, and a lookup without a group reused the previous one (or failed on the first lookup). It is now per lookup, and a lookup without a group uses the `default` secret group (documented + upgrade guide). - **Spring Cloud Config**: the remainders cache iterated by the reload task is now synchronized, and the task iterates a snapshot. - Hashicorp Vault is handled separately in #27669 (CAMEL-25518) and #27679 (CAMEL-25552). Tests: new `IBMSecretsManagerPropertiesFunctionTest` (fake `SecretsManager` client, no cloud access) verifies the group used per lookup and the read-only secrets view; existing dev console / reload task unit tests in the AWS, Azure and Google modules pass. Fixes [CAMEL-25553](https://issues.apache.org/jira/browse/CAMEL-25553) _Claude Code on behalf of davsclaus_ 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- 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]
