Deploy key tracking/cleanup #388

New Issue

2026-07-16T15:45:21-04:00

didericis commented

2026-07-16 15:45:21 -04:00

When starting a new bot bottle, I've frequently ran into "deploy key collision error" problems. This is because as I've been developing, I've forgotten about other images I've partially spun up and then had error, or bottles that failed partway during installation, or simply other bottles I've started on other machines. I eventually want to have all of the following mitigations:

Agent names should include the host name in them so we don't get those collisions
There should be a record of deploy keys we've created stored on the host machine db, and eventually copied to the cloud console db so we can cleanup any stray deploy keys
If there is a deploy key collision error, we should fail more gracefully, and allow the user to decide whether to a) continue with an appended random slug (default behavior) b) delete the key with the collision before proceeding c) quit/try another agent name

When starting a new bot bottle, I've frequently ran into "deploy key collision error" problems. This is because as I've been developing, I've forgotten about other images I've partially spun up and then had error, or bottles that failed partway during installation, or simply other bottles I've started on other machines. I eventually want to have all of the following mitigations: 1. Agent names should include the host name in them so we don't get those collisions 2. There should be a record of deploy keys we've created stored on the host machine db, and eventually copied to the cloud console db so we can cleanup any stray deploy keys 3. If there is a deploy key collision error, we should fail more gracefully, and allow the user to decide whether to a) continue with an appended random slug (default behavior) b) delete the key with the collision before proceeding c) quit/try another agent name

didericis added the Kind/Feature label 2026-07-16 15:45:46 -04:00

didericis added the

Priority

Low

4

label 2026-07-16 22:19:38 -04:00

didericis-claude was assigned by didericis

2026-07-16 22:23:55 -04:00

didericis commented

2026-07-16 22:24:12 -04:00

@didericis-claude we should split this into 3 separate PRs. Let's do the first one now, easy win.

didericis referenced this issue from a commit

2026-07-16 22:27:18 -04:00

feat(git-gate): include hostname in deploy key title

didericis-claude referenced a pull request that will close this issue

2026-07-16 22:27:24 -04:00

feat(git-gate): include hostname in deploy key title #393

didericis-claude commented

2026-07-16 22:27:36 -04:00

Done — PR #393 implements part 1. Deploy key titles now include the machine hostname:

bot-bottle:<hostname>:<slug>:<repo-name>

Keys created on different machines will no longer share the same title, so abandoned keys from another host won't cause a collision on the next launch.

Done — PR #393 implements part 1. Deploy key titles now include the machine hostname: ``` bot-bottle:<hostname>:<slug>:<repo-name> ``` Keys created on different machines will no longer share the same title, so abandoned keys from another host won't cause a collision on the next launch.

didericis referenced this issue from a commit

2026-07-16 23:07:16 -04:00

feat(git-gate): include hostname in deploy key title

didericis closed this issue

2026-07-16 23:34:11 -04:00

didericis reopened this issue

2026-07-16 23:34:17 -04:00

Sign in to join this conversation.