Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Azure secret doc enhancement #23079

Merged
merged 5 commits into from
Sep 21, 2023
Merged

Azure secret doc enhancement #23079

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
7165010
* azure secret doc enhancement
maxcoulombe Sep 14, 2023
d15e9d8
+ added changelog
maxcoulombe Sep 14, 2023
181973b
Update website/content/docs/secrets/azure.mdx
maxcoulombe Sep 15, 2023
bd2c23a
Merge remote-tracking branch 'origin/main' into azure-doc-improvement
maxcoulombe Sep 15, 2023
919b731
* removed changelog
maxcoulombe Sep 15, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions website/content/docs/secrets/azure.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,6 +23,15 @@ The password will be deleted when the lease is revoked.

## Setup

<Note>

You can configure the Azure secrets engine with the Vault API or
established environment variables such as `AZURE_CLIENT_ID` or
`AZURE_CLIENT_SECRET`. If you use both methods, note that
environment variables always take precedence over API values.

</Note>

Most secrets engines must be configured in advance before they can perform their
functions. These steps are usually completed by an operator or configuration
management tool.
Expand Down
Loading