Request - add start-on-deploy flag to [deploy] section

Open
#3,137 0 comments 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 by locating the fly deploy handling and the TOML [deploy] configuration parsing. Check how the minimum number of machines is determined and how stopped apps are treated. Done means a start-on-deploy setting can make deploy start at least the configured minimum machines, with behavior covered by appropriate tests.

Written by the indexing model from the issue text.

Description

bug

Describe the bug
If all machines for an app are down, doing a fly deploy will not start new machines. This can be desireable behavior, but it could also be useful to always start machines after a deploy.

** Suggestion**
In the [deploy] section of the toml, add a new flag along the lines of start-on-deploy, which, if true, will always start (at least) the minimum number of machines configured for the app.

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.