-
Notifications
You must be signed in to change notification settings - Fork 104
Update Azure Static Secrets docs #1246
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.
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
base: main
Are you sure you want to change the base?
Conversation
Vercel Previews Deployed
|
Broken Link CheckerNo broken links found! 🎉 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| You can read metadata values from the `/azure/static-roles/:name` and | |
| `/azure/static-creds/:name` endpoints. When you fetch credentials, Vault | |
| merges the role metadata with any additional metadata provided in the | |
| request, but role metadata always takes precedence if keys overlap. |
Style correction: write in active voice
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| Vault merges the path metadata with metadata stored with the role, but | |
| role metadata always takes precedence when keys overlap. Key/value pairs | |
| appear as strings separated by the `=` symbol (e.g. `key=value`). When | |
| using the Vault CLI, you can provide multiple tags in the role | |
| configuration by adding multiple `metadata` assignments in the same command. |
Style correction: write in active voice
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| - `skip_import_rotation` (`bool`, `false`) - Determines whether Vault | |
| generate credentials automatically when creating a role. Set `skip_import_rotation` | |
| to `true` if you do not want Vault to create initial credentials on role | |
| creation. If you skip credential creation, you can generate them later manually | |
| rotating to role with the `rotate-role` parameter or by importing the | |
| credentials from a trusted source. | |
| If you omit `skip_import_rotation` or set it to `false`, Vault automatically | |
| provisions the first set of credentials during role creation. |
Style correction: write in active voice
No description provided.