Zum Inhalt springen
#0737
ContainersDaemonNotifications

Rotate the breached key across eighty customers before lunch

Tuesday, 9:04 AM. The payments vendor emails: your API key appeared in a breach dump, rotate immediately. The key lives in eighty customer containers as an environment variable.

You write a twelve-line loop. For each container, PUT /api/v1/containers/{id}/env merges the new key: the write lands in /etc/environment and in the runtime environment new sessions see. Running workers don't re-read their environment, so the loop also POSTs the worker daemon's stop, then its start. Fresh process, fresh key.

Eighty containers, 240 requests, eleven minutes. The last iteration fires a notification to your phone: rotation complete. You reply to the vendor's email before the coffee is cold.

No SSH into eighty machines, no config redeploy. The environment is an API, so the rotation is a loop.

The environment is an API, so the rotation is a loop.