mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-06 10:59:59 +00:00
Six assertions: the key is persisted on the deploy that creates it, it is loaded before the logins that may need it, recovery is gated on both logins having failed and a key existing, the rebuilt AppRole is the inventory one rather than the recorded one, the recovery path ends by re-pinning, and a rejected key fails loudly. Recovering to the recorded pair instead of the inventory pair would strand the next deploy the same way, which is why that one is asserted directly.