Skip to content

Conversation

@Zlaticanin
Copy link
Contributor

No description provided.

@Zlaticanin Zlaticanin requested a review from a team as a code owner November 5, 2025 22:07
@github-actions github-actions bot added the Vault Content update for Vault product docs label Nov 5, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Nov 5, 2025

Vercel Previews Deployed

Name Status Preview Updated (UTC)
Dev Portal ✅ Ready (Inspect) Visit Preview Wed Nov 5 22:29:51 UTC 2025
Unified Docs API ✅ Ready (Inspect) Visit Preview Wed Nov 5 22:23:33 UTC 2025

@github-actions
Copy link
Contributor

github-actions bot commented Nov 5, 2025

Broken Link Checker

No broken links found! 🎉

Comment on lines 466 to 468
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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

Comment on lines 599 to 602
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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

Comment on lines 475 to 478
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- `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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Vault Content update for Vault product docs

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants