Option to create a config file from `fly pg create`

Open
#3,775 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
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
go
Domain
cli

Research direction

Start at the fly pg create command entry point and read how its -c and --app options currently work. Define the generated fly.pg.toml contents and verify that it records the database and supports managing app resources through -c instead of --app.

Written by the indexing model from the issue text.

Description

enhancement

From a DX perspective it would make sense to me if there was a "declarative" record of the database. I think it'd be a nice feature if you could either by default or by means of a flag have a fly.pg.toml generated.

That way:

  • you could manage the app resources through the -c flag rather than the --app flag
  • the database is 'visible' as a configuration
  • the mental model for what a database actually is underneath is a bit easier
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.