doc: fix documentation types based on reviewdog checks

Signed-off-by: Ilya Katlinski <ilya.katlinsky@gmail.com>
This commit is contained in:
Ilya Katlinski
2023-08-08 12:23:43 +02:00
parent ad9544c483
commit 1dd90e437c
3 changed files with 3 additions and 3 deletions
+1 -1
View File
@@ -3,4 +3,4 @@
'@backstage/plugin-vault': minor
---
Added ability to override vault secretEngine value on catalog entity level using annotation `vault.io/secrets-engine`
Added ability to override vault secret engine value on catalog entity level using annotation `vault.io/secrets-engine`
+1 -1
View File
@@ -106,7 +106,7 @@ The path is relative to your secrets engine folder. So if you want to get the se
You will set the `vault.io/secret-path` to `test/backstage`. If the folder `backstage` contains other sub-folders, the plugin will fetch the secrets inside them and adapt the **View** and **Edit** URLs to point to the correct place.
In case you need to support different secret engines for entities of the catalog you can proivde optional annotion to the entity in `catalog-info.yaml`:
In case you need to support different secret engines for entities of the catalog you can provide optional annotation to the entity in `catalog-info.yaml`:
```diff
apiVersion: backstage.io/v1alpha1
+1 -1
View File
@@ -87,7 +87,7 @@ If the annotation is missing for a certain component, then the card will show so
![Screenshot of the vault plugin with missing annotation](images/annotation-missing.png)
In case you need to support different secret engines for entities of the catalog you can proivde optional annotion to the entity in `catalog-info.yaml`:
In case you need to support different secret engines for entities of the catalog you can provide optional annotation to the entity in `catalog-info.yaml`:
```diff
apiVersion: backstage.io/v1alpha1