Split out of #205 so the vault's claim can land first. networkmanager, systemd-networkd and dhcpcd declare uplink-networkmanager, uplink-systemd-networkd and uplink-dhcpcd; the host reports the one it finds active (mesh-host #61, rolled). Merge only once every machine running one of these has reported a profile carrying it — the laptop node's report after its last apply was lost ("could not tell the mesh: reporting: context canceled"), so it has not yet.
Split out of #205 so the vault's claim can land first. `networkmanager`, `systemd-networkd` and `dhcpcd` declare `uplink-networkmanager`, `uplink-systemd-networkd` and `uplink-dhcpcd`; the host reports the one it finds active (mesh-host #61, rolled). Merge only once every machine running one of these has reported a profile carrying it — the laptop node's report after its last apply was lost ("could not tell the mesh: reporting: context canceled"), so it has not yet.
The vault's claim makes a second provider of secret a second claimant, refused by name. The three
uplink definitions declare uplink-networkmanager, uplink-systemd-networkd and uplink-dhcpcd, which the
host reports for the manager it finds active, so the holder for a manager the machine does not run
is refused the way any missing capability is. Merges after the controller holds the seat and the host
reports the capability.
A module publishes under its own name only; secret.provisioned read as another module's event and the
builder refused the vault's definition today, so the seat claim could not be built. The three events lose
the prefix; nothing outside the vault listens for the old names.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Split out of #205 so the vault's claim can land first.
networkmanager,systemd-networkdanddhcpcddeclareuplink-networkmanager,uplink-systemd-networkdanduplink-dhcpcd; the host reports the one it finds active (mesh-host #61, rolled). Merge only once every machine running one of these has reported a profile carrying it — the laptop node's report after its last apply was lost ("could not tell the mesh: reporting: context canceled"), so it has not yet.