Add global `--debug` flag to enable debug logs (ala `LOG_LEVEL=debug`)

Open
#583 5 comments 5 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

No files or tests are named. Start by tracing flyctl's global flag handling and how LOG_LEVEL=debug is consumed across the API, build, remote-builder, and WireGuard paths; done means a common debug-style flag enables equivalent logs, with any error guidance agreed and covered by tests.

Written by the indexing model from the issue text.

Description

enhancement good first issue good small task

The debug logs are useful for diagnosing issues with the api, builds, remote builders, wireguard, etc. Unfortunately an env variable isn't discoverable so nobody knows about them. We should enable them from a common global flag that people already expect to help with debugging, like --debug, --verbose, --trace, etc.

We might also want to print a message on error instructing the user to try again with that flag.

Hopefully exposing debug logs will help folks figure out issues before heading to the forum or giving up.

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.