All committers have signed the CLA.

Gentle bump, could you please review this? 🙏🏼

Hi, would you say this review accomplishes the same objective of allowing users to read all properties of a secret at once?

If yes, I think it'd be preferable to focus on #238 as I find the added functionality of being able to optionally add a prefix useful to avoid collisions and group related secret properties.

@maxcoulombe I haven't tested out #238. It could work as well although the actual use case might be different.
This PR would allow us to get dynamic secrets from Vault.
This would be an example:

secrets: |
          postgres/creds/dbname * | DB_CRED;

The trick with dynamic secrets is that you can only make 1 request. Every additional request is going to generate different values.
If #238 can do the same with 1 request only, and stores the keys with a prefix, then yes, let's go for that.
Anything that would unblock this thing.

Closing as this should be fixed by #488.

Please feel free to reopen if you feel this was a mistake, or if there is additional information to add. Thanks!