How would you roll back the app while keeping current infrastructure?

Say it in 30 seconds

Say it like this (20-30 seconds)

I choose a known compatible published image and deploy it using the current infrastructure code. MiniTickets exposes an image_tag input for that operation, while SSM records which image version should run. This avoids applying an old infrastructure checkout that could remove newer resources. I check schema and event compatibility first, then verify the running revisions and user path. Rollback is another deployment, with its own failure modes.

The deeper answer

There are separate version axes: application artifacts, infrastructure code, database schema and queued event formats. An old image is usable only if it still understands the current state it will encounter.

A manual CD run on main with an existing image tag skips publication and uses main’s infrastructure checkout. Phase B changes the shared SSM image tag; the infrastructure program reads that value for the services. The committed stack file describes environment shape rather than storing release image overrides.

An image rollback may restore application behavior while leaving an additive schema change in place. It will not unsend emails, restore deleted data or undo accepted bookings. I would verify the affected business behavior and watch queues after the rollback, not rely only on a green workflow. If the old image cannot handle the new schema or queued events, a forward fix may be the safer recovery.

Counter-questions

Should you approve an older waiting workflow?

No. That can use an older infrastructure checkout. Start the documented manual image deployment from current main instead.

Does changing the SSM tag prove recovery?

No. It records desired version. Confirm ECS revisions, Lambda images, triggers and the affected request path.

How do you keep rollback images?

The registry retention design preserves deployed tags. Check the exact desired artifact still exists before beginning recovery.

Where in MiniTickets

Read the path chapter, select the relevant map piece →, then inspect infra/src/release.ts → readDeployedImageTag. Work through the related case for a diagnostic example.