Skip to content

docs: add get key permission requirement for Azure Key Vault when version is omitted#2122

Merged
felixfontein merged 3 commits intogetsops:mainfrom
Hanashiko:main
Apr 8, 2026
Merged

docs: add get key permission requirement for Azure Key Vault when version is omitted#2122
felixfontein merged 3 commits intogetsops:mainfrom
Hanashiko:main

Conversation

@Hanashiko
Copy link
Copy Markdown
Contributor

Summary

Fixes #2112

When the key version is omitted from the Azure Key Vault URL (trailing slash), SOPS resolves the latest key version via the Azure Key Vault API. This requires the get key permission in addition to encrypt and decrypt, which was not mentioned in the documentation.

Changes:

  • Added get tot he recommended az keyvault set-policy --key-permissions command
  • Added a note explaining wht get is needed and the trade-off with explicit versioning

Copy link
Copy Markdown
Contributor

@felixfontein felixfontein left a comment

Choose a reason for hiding this comment

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

Thanks for your contribution! Please note that you must sign-off your commits, otherwise this cannot be merged. Thanks.

Comment thread README.rst
Comment thread README.rst Outdated
@felixfontein
Copy link
Copy Markdown
Contributor

CI failures are unrelated, see #2123.

@felixfontein
Copy link
Copy Markdown
Contributor

Ping @Hanashiko

…sion is omitted

Signed-off-by: Hanashiko <hlichisper@gmail.com>
@Hanashiko
Copy link
Copy Markdown
Contributor Author

Sorry for the delay in responding; I believe I've taken the changes you mentioned into account

Signed-off-by: Felix Fontein <felix@fontein.de>
@felixfontein felixfontein merged commit f11139e into getsops:main Apr 8, 2026
19 checks passed
@felixfontein
Copy link
Copy Markdown
Contributor

@Hanashiko thanks for improving this!

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Azure Key Vault documentation should mention get key permission is needed when key version is omitted

2 participants