paulononato/backstage
1
0
Fork 0
Code Issues Pull Requests Actions 40 Packages Projects Releases Wiki Activity

chore: add changeset record for vault plugin changes

Browse Source 
Signed-off-by: Ilya Katlinski <ilya.katlinsky@gmail.com>
This commit is contained in:
Ilya Katlinski
2023-08-08 09:06:03 +02:00
parent 49c3657ac6
commit 858a188008
3 changed files with 8 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.changeset/silent-numbers-retire.md
+6
View File
@@ -0,0 +1,6 @@
---
'@backstage/plugin-vault-backend': minor
'@backstage/plugin-vault': minor
---
Added ability to override vault secretEngine value on catalog entity level using annotation `vault.io/secrets-engine`
plugins/vault-backend/README.md
+1 -1
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/secret-engine: customSecretEngine # Optional. By default it uses 'secertEngine' value from configuration.
+ vault.io/secrets-engine: customSecretEngine # Optional. By default it uses 'secertEngine' value from configuration.
```
That will overwrite the default secret engine from the configuration.
plugins/vault/README.md
+1 -1
View File
@@ -96,7 +96,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/secret-engine: customSecretEngine # Optional. By default it uses 'secertEngine' value from configuration.
+ vault.io/secrets-engine: customSecretEngine # Optional. By default it uses 'secertEngine' value from configuration.
```
That will overwrite the default secret engine from the configuration.