feat: adopt vault api signature calls based on proposal

Signed-off-by: Ilya Katlinski <ilya.katlinsky@gmail.com>
This commit is contained in:
Ilya Katlinski
2023-09-10 07:20:10 +02:00
parent 03947ee72a
commit 1bdcf6bb7a
8 changed files with 34 additions and 19 deletions
+2 -2
View File
@@ -115,7 +115,7 @@ In case you need to support different secret engines for entities of the catalog
# ...
annotations:
vault.io/secrets-path: path/to/secrets
+ vault.io/secrets-engine: customSecretEngine # Optional. By default it uses 'secertEngine' value from configuration.
+ vault.io/secrets-engine: customSecretEngine # Optional. By default it uses the 'secretEngine' value from your app-config.
```
That will overwrite the default secret engine from the configuration.
@@ -152,7 +152,7 @@ export default async function createPlugin(
## Features
- List the secrets present in a certain path
- Use different secret engines for different components
- Use different secret engines for different entities
- Open a link to view the secret
- Open a link to edit the secret
- Renew the token automatically with a defined periodicity