6 Commits

Include renames

Author	SHA1	Message	Date
kebandClaude Opus 5.5	411068ba43	feat: the right pane describes what's selected in the pane you're in ... Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>	2026-10-11 10:49:39 +02:00
keb	c8abc1dc95	feat: the value's keys on the line below it: reveal and copy (#8)	2026-10-11 10:38:00 +02:00
keb	71396f1e02	feat: a Fields pane for anything but a secret, first for Azure accounts: fields and groups to move through, filter and copy (#7)	2026-10-11 10:37:40 +02:00
keb	52b6257dd5	feat: show who an Azure account signs in as, in Details on its row (#5) ... On an Azure account's group row, the Details pane now describes the account: | field | from | |---|---| | name | token `name` | | user (and "service principal") | az's account list | | tenant: name · ID | az's account list (the name is borrowed from another entry in the same tenant when az left it out) | | object ID | token `oid`; `y` on the row copies it | | sign-in: MFA or not, and how | token `amr` | | directory roles | token `wids`: built-in roles by name, others as `role 1a2b3c4d`, the default member role left out | | subs: count · default | az's account list | | cloud | az's account list, when not AzureCloud | Nothing is fetched for it: the claims are the ones from the token lazysecrets already gets for the account's own tenant, read without verification. The token itself is never stored or shown. Before the first token, only the az-list fields show. A failing account shows its sign-in problem there instead (from #4). New optional `provider.Accounts` interface; `azure.Provider` implements it. Tests: the fields from claims and az's list, sign-in methods, the UI showing it on the group row only, and `y` copying the object ID. Checked against a real signed-in account (name, MFA · password, default subscription) and an expired one (az-list fields only, since there's no token). 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Karl-Einar Bergstrøm <karl-einarb@outlook.com> Reviewed-on: #5	2026-10-11 10:09:17 +02:00
keb	a82f6bff27	fix: say a sign-in error once, then in Details for that account (#4) ... A failing account's error ("sign-in required … press L to run az login --tenant …") stayed in the footer for the whole session. - **Footer:** it's now an ordinary message, shown once when an account's error first appears (at start, or when a load fails), and gone on the next key press. It's said again only when the errors change, or for another account. - **Details:** with that account's group header or one of its sources selected, the Details pane shows the error and the sign-in hint, in place of "Select a vault or scope…". - **`L`** signs in to the selected account when it needs it, else to the last one that asked, as before. With two accounts, `L` used to run whichever sign-in had failed most recently. Test: two accounts, one failing to list its subscriptions. The message is in the footer at start and gone after a key press, in Details on that account's group, and `L` targets it. It isn't shown on the other account's rows. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Karl-Einar Bergstrøm <karl-einarb@outlook.com> Reviewed-on: #4	2026-10-11 10:06:28 +02:00
kebandClaude Opus 5.5	6fab41703e	Hello world 👋 ... Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>	2026-10-10 23:58:25 +02:00