flyctl config validation improvements

Open
#3,583 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by locating flyctl's existing configuration-validation entry point and read the overlapping-port change in commit 8d86c0c35dd7a49e1628fbce87e74eba85ea34a1. Check how validation coverage is organized, then cover overlapping port definitions and auto-start requested on UDP; done means both unsupported combinations are reported before deployment.

Written by the indexing model from the issue text.

Description

enhancement

From https://community.fly.io/t/fly-config-in-your-choice-of-formats-toml-yaml-or-json/20017/7 :

I wish flyctl would actually go further and also complain ahead of time about settings combinations that other parts of the Fly infrastructure will consider illogical/invalid:

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.