oscerd opened a new pull request, #25013: URL: https://github.com/apache/camel/pull/25013
### Motivation [CAMEL-21955](https://issues.apache.org/jira/browse/CAMEL-21955). IBM Secrets Manager was the only supported secrets backend without a dev console — AWS Secrets Manager, HashiCorp Vault and Kubernetes all ship one. ### Changes New `SecretsDevConsole` (`ibm-secrets`) in `camel-ibm-secrets-manager`, following the same shape as the AWS console. Everything it needs already existed: - `IBMSecretsManagerPropertiesFunction` registers as `ibm` and exposes `getSecrets()`. - `IBMEventStreamReloadTriggerTask` exposes `getLastCheckTime()` / `getLastReloadTime()` / `getUpdates()` — the same API the AWS console consumes from its CloudTrail task. Reported in both text and JSON output: - Service URL, and `Login: IAM Token` - Whether refresh is enabled, and when it is, the Event Stream topic and bootstrap servers - Last check / last reload times from the reload trigger task - Secrets in use, sorted, with their last-update age **No secrets are printed.** Consistent with the existing consoles, only non-sensitive configuration is reported — the IAM token and the Event Stream password are never emitted; the login is described by kind (`IAM Token`) rather than by value. `camel-util-json` is added to the module's dependencies for `JsonObject`/`JsonArray`, matching how `camel-aws-secrets-manager` declares it. ### Testing - `mvn install` in `components/camel-ibm/camel-ibm-secrets-manager`: BUILD SUCCESS, 8 tests pass (the integration tests are skipped without IBM credentials). - Dev-console SPI metadata generated as expected, and the catalog picked up the new `ibm-secrets` console entry. - Full reactor `mvn clean install -DskipTests` from root: success, all generated files committed. Main-only (4.22.0), additive — no backport. _Claude Code on behalf of Andrea Cosentino (@oscerd)._ 🤖 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]
