luxolus
/
open-vault
2
0
Fork 0
Code Issues 1 Pull Requests Releases Activity

docs: fix formatting in azure secrets overview (#12058)

This commit is contained in:
Jason O'Donnell 2021-07-13 14:55:53 -04:00 committed by GitHub
parent fc8914db16
commit 8bc9790bf4
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 14 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
website/content/docs/secrets/azure.mdx
View File

@ -29,7 +29,7 @@ management tool.
1. Enable the Azure secrets engine:
```text
```shell
$ vault secrets enable azure
Success! Enabled the azure secrets engine at: azure/
```
@ -39,12 +39,12 @@ management tool.
1. Configure the secrets engine with account credentials:
```text
```shell
$ vault write azure/config \
subscription_id=$AZURE_SUBSCRIPTION_ID \
tenant_id=$AZURE_TENANT_ID \
client_id=$AZURE_CLIENT_ID \
client_secret=$AZURE_CLIENT_SECRET
subscription_id=$AZURE_SUBSCRIPTION_ID \
tenant_id=$AZURE_TENANT_ID \
client_id=$AZURE_CLIENT_ID \
client_secret=$AZURE_CLIENT_SECRET
Success! Data written to: azure/config
```
@ -58,7 +58,9 @@ management tool.
To configure a role called "my-role" with an existing service principal:
```shell-session
$ vault write azure/roles/my-role application_object_id=<existing_app_obj_id> ttl=1h
$ vault write azure/roles/my-role \
application_object_id=<existing_app_obj_id> \
ttl=1h
```
Alternatively, to configure the role to create a new service principal with Azure roles:
@ -140,7 +142,11 @@ Group specification by name must yield a single matching group.
Example of role configuration:
```shell-session
$ vault write azure/roles/my-role ttl=1h max_ttl=24h azure_roles=@az_roles.json azure_groups=@az_groups.json
$ vault write azure/roles/my-role \
ttl=1h \
max_ttl=24h \
azure_roles=@az_roles.json \
azure_groups=@az_groups.json
$ cat az_roles.json
[