Report the key state of an AshVault scope: which provider serves it, what it is called there, its current version, when that version was minted, which historical versions are still fetchable, and whether the scope has been crypto-erased.
This task is read-only in the strongest sense: it never mints key material.
AshVault.KeyProvider.current_key/1 mints version 1 on first use, so an unused scope is
detected with get_key/2 first and reported as not_minted without creating anything.
Usage
mix ash_vault.key_info MyApp.Accounts.User --tenant acme
mix ash_vault.key_info MyApp.Accounts.User --all-tenants MyApp.Accounts.list_tenant_ids/0
mix ash_vault.key_info MyApp.Notes # a `scope :global` resourceOptions
--tenant TENANT required when the key scope is `:tenant`
--all-tenants MFA zero-arity `Module.function/0` listing tenants
--domain MODULE Ash domain (inferred from `:ash_domains` when omitted)Output
ash_vault.key_info=scope resource=MyApp.Accounts.User tenant=acme scope=acme \
vault=MyApp.Vault provider=AshVault.KeyProviders.OpenBao key_name=ashvault-acme \
status=active version=3 created_at=2026-02-01T10:12:00Z versions=1,2,3
MyApp.Vault: scope acme is active at key version 3 (3 version(s) retained).status is one of active, not_minted or destroyed. A destroyed scope exits 0 —
a tombstone is a legitimate answer, not a failure.