Attach operator keys to builders so none gets an emailed root password
The controller created every builder without a DigitalOcean account key, so DigitalOcean set a root password, emailed it to the token's owner, and turned password logins on: one email and one password-reachable box per builder, 146 of them on Oct 8. DO_SSH_KEYS lists account key IDs attached at creation (Ryan, DHH and Emir in the template). It needs ssh_key:read on the controller's token; without it every create is refused with 403, so it stays empty until the token has it. Builders also turn password SSH off in cloud-init, which holds even while no account key is attached, and Emir joins the operators whose GitHub keys reach root.
This commit is contained in:
1 parent
e34944e9fb
commit
7e86af28b3
6 files changed
+26
-4
No files matched your search
@@ -17,3 +17,8 @@ LOCK=/run/omarchy-controller/lock
|
||||
# Operator public keys for root on every builder droplet (JSON array).
|
||||
# create.sh fills this from the operators' GitHub keys.
|
||||
SSH_KEYS_JSON=[]
|
||||
# DigitalOcean account SSH key IDs attached to every builder (JSON array), so
|
||||
# DigitalOcean does not email a root password for each one. Needs ssh_key:read
|
||||
# on DIGITALOCEAN_TOKEN. List them with: doctl compute ssh-key list
|
||||
# Ryan R. Hughes, DHH, Emir.
|
||||
DO_SSH_KEYS=[59143572,59143588,59779105]
|
||||
Reference in new issue
Block a user