1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
//! The picker's read-back of the assignment it is about to change (§9.4,
//! bl-53be): brazen's provider rows joined onto `providers.yaml`'s roles, into
//! "why can this role not be fired?". Coverage-excluded glue — the judgement
//! itself is [`role_fault`](crate::model_pick::role_fault).
use ;
use crate;
use crate;
/// Every declared role paired with why it cannot be fired (§9.4): the row it
/// dispatches through is not one brazen's table has. An unusable assignment is
/// visible at the point of change instead of failing at fire.
///
/// **It read the global `models.yaml` too until bl-d9cb**, for a judgement about
/// a table lernie no longer loads — so the picker is down to one file, on the
/// read side as well as the write side.
pub
/// brazen's effective provider rows, asked once per open (§5.3). The set is
/// brazen's fact, read through the linked `--list-providers` projection so the
/// built-in rows a `config.toml` scan would miss are included.
///
/// Handed back **whole**. Two questions are asked of one read: which rows exist
/// (the dropdown and the §9.2 gate, which want [`row_names`]) and what the
/// selected row needs when it cannot answer (the credential fault's
/// [`remedy`](crate::model_pick::remedy), which wants its `auth` column).
pub