Kevin Wooten

@Sharofiddin Sorry for the late reply! The Vault extension is working properly with this support; it's just that requesting the username from a key-value secret store is not supported. Currently...

This will require changing the type of the `kvKey` config property to an Optional (to allow for deprecation). This means this will have to go into the `3.0` release.

How many REST calls are made to IAM? Is it something we can ourselves? If it's 2 or 3 simple REST calls then maybe just use the Vert.x WebClient. I'm...

Forgive me, I have not gone through your PR yet. I was just suggesting that off the top of my head. So basically we only need to get the AWS...

I think Go's AWS packages have a completely separate package for getting credentials and even one for using the credentials endpoint. Have you checked for that with Java?

@yuriytkach Both `Aws4Signer` and `DefaultCredentialsProvider` are in `software.amazon.awssdk:auth` which has a fairly small POM. The biggest dependency is AWS's `sdk-core` but that's fairly small (both by # of classes and...

@yuriytkach I think much of this can/should be moved to the new client in #215. What do you think? We'll still need the Quarkus configuration parts but all the api...

I am not sure what you mean "deactivates" a secret. A secret is store at a "path". Deleting a secret is akin to deleting its path.

Sorry, I forgot that deleted KV secrets can be undeleted for a period of time before they are fully removed completely.

@aaronz-vipaso That would be 1 thing that needs to happen. Additionally the `CertificateData` class would need to be updated to be able to handle that format and the API requests...