Fly.io CI Deployment Control

Overview

Build CI as a controlled release system rather than a single deploy command. Separate pull-request validation from authenticated deployment, bind production to an immutable revision, and retain enough evidence to identify and reverse the release.

Prerequisites

• Named app, organization, environment, release owner, and rollback owner
• Protected CI environment with an approved secret manager
• Health endpoint or other deployment check and a tested prior release

Instructions

Step 1: Separate validation from deployment

Run secret-free configuration, container, and contract checks on pull requests. Permit authenticated Fly.io access only in a protected post-merge or manually approved environment.

Step 2: Issue the narrowest token