Skip to content

Commit

Permalink
docs: fix broken link in getting-started/usage page (#692)
Browse files Browse the repository at this point in the history
Co-authored-by: Anish Ramasekar <anish.ramasekar@gmail.com>
  • Loading branch information
christianfosli and aramase committed Oct 26, 2021
1 parent adb7285 commit e34837b
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion website/content/en/getting-started/usage/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -72,7 +72,7 @@ To provide identity to access key vault, refer to the following [section](#provi
| objects | yes | a string of arrays of strings | "" |
| objectName | yes | name of a Key Vault object | "" |
| objectAlias | no | [__*available for version > 0.0.4*__] specify the filename of the object when written to disk - defaults to objectName if not provided | "" |
| objectType | yes | type of a Key Vault object: secret, key or cert.<br>For Key Vault certificates, refer to [doc](../../configurations/getting-certs-and-keys.md) for the object type to use.</br> | "" |
| objectType | yes | type of a Key Vault object: secret, key or cert.<br>For Key Vault certificates, refer to [doc](../../configurations/getting-certs-and-keys) for the object type to use.</br> | "" |
| objectVersion | no | version of a Key Vault object, if not provided, will use latest | "" |
| objectFormat | no | [__*available for version > 0.0.7*__] the format of the Azure Key Vault object, supported types are pem and pfx. `objectFormat: pfx` is only supported with `objectType: secret` and PKCS12 or ECC certificates | "pem" |
| objectEncoding | no | [__*available for version > 0.0.8*__] the encoding of the Azure Key Vault secret object, supported types are `utf-8`, `hex` and `base64`. This option is supported only with `objectType: secret` | "utf-8" |
Expand Down

0 comments on commit e34837b

Please sign in to comment.