feat: a vault's settings come with the vault list, with no requests of their own
CI / Checks (pull_request) Successful in 24s
PR title / Conventional title (pull_request) Successful in 2s

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
kebandClaude Opus 5.5 committed 2026-10-11 13:42:48 +02:00
1 parent 5381cf5d43
commit 879b961ac5
6 files changed
+157 -94

No files matched your search

+5 -6
View File
@@ -65,9 +65,8 @@ key (PEM public key) or certificate; private key material is never
fetched. `v` lists an item's versions. Items expiring within
`expiryWarningDays` (30 by default) are marked `⚠ 12d`, expired ones `✗`.
On a vault, the right pane shows its settings from the Key Vault
management API: resource group, location, SKU, whether access is by Azure
roles or access policies, soft delete and purge protection, which networks
can reach it, private endpoints and tags. They load the first time you're
on the vault (`r` in the Vaults pane loads them again), and need read
access to the vault resource, as discovering it does.
On a vault, the right pane shows its settings: resource group, location,
SKU, whether access is by Azure roles or access policies, soft delete and
purge protection, which networks can reach it, private endpoints and tags.
They come with the list of vaults, so they cost no extra requests and are
cached with it.