Launch Apps: Warn when working with apps that contain multiple image versions

Open
#2,808 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
go
Domain
cli

Research direction

Start with Flyctl's launch and deploy flows, focusing on how Launch machines and their deployed image versions are observed. Determine how to identify an app whose machines use different image versions and define when the warning should appear. Verify the behavior with a deployment that leaves multiple versions running.

Written by the indexing model from the issue text.

Description

apps-v2 enhancement good small task ux-annoying

Sometimes things go wrong! For example, an app might expect a secret or env variable, and crash part of the way through a deploy. This leaves you with an app that has two deployed image versions at the same time, which isn't clear and leads to unexpected behavior.

It'd be nice if Flyctl was smart enough to warn you when working with an app if it sees anything obviously wrong, such as a Launch machine that has a different image version from its peers.

Dominant language
Go
Stars
1.7k
Forks
311
Avg merge
12h 50m
Merged PRs (30d)
78

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from superfly/flyctl

All issues in superfly/flyctl

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.