Some operations shouldn’t need a person. CI runs, automated deploys, and
scheduled tasks all act on the fleet, and today they borrow a human’s identity to
do it. A dedicated celilo-bot service account gives automation its own
identity — one that machines can use and operators can reason about.
Why a dedicated identity
When automation acts as a human, you lose the line between what a person did and what a pipeline did. Audit trails blur, and revoking access means disrupting a real operator. A distinct service account fixes both: automated actions are attributable to the automation, and its access can be scoped, rotated, or revoked on its own terms without touching anyone’s personal credentials.
For CI/CD and automation
The intended users are the non-interactive paths — continuous integration, automated delivery, and any workflow that operates the fleet without a human at the keyboard. Giving those paths a first-class account of their own is what lets them run headlessly and safely, rather than being wedged into an identity model built for people.