Add support for Jackson 3 in secret manager plugin

[jamesmudd]

Describe the feature

Currently using the secret manager plugin requires Jackson 2 on the classpath for loading the secret data.

In Spring Boot 4 Jackson 3 is now used by default, so probably will significantly increase in usage soon. I think it should be possible to implement this in a backwards compatible way by checking the availability of Jackson2 or Jackson3 in AwsSecretsManagerConnectionPluginFactory then calling into a specific impl of AwsSecretsManagerConnectionPlugin.

I could maybe have a go at an impl but wanted to understand if this is something that might get merged, or would you have a preferred approach for this e.g. abstracting all JSON serialisation behind a AWS interface?

Use Case

Using the AWS JDBC driver with the secret manager plugin in Spring Boot 4

Proposed Solution

No response

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

The AWS Advanced JDBC Wrapper version used

3.0.0

JDK version used

25

Operating System and version

linux ECS Fargate