FLY_ORG is not respected by org-level commands

TL;DR

Upgrade flyctl to the latest version (fly version upgrade) and FLY_ORG will be respected by org-level commands. This was a bug in flyctl v0.1.83; a fix was merged and confirmed by the maintainer.

Steps

1. Issue superfly/flyctl#2757 (closed, 8 comments): Describe the bug Briefly, describe what broke and provide the following details: Setting the FLY_ORG env var does not replace -o in org-level commands. According to @michaeldwan, this is a bug: https://community.fly.io/t/flyctl-feature-request-fly-org-env-var/15099/4. Operating system fly version

2. ** Command output: ** ```text ❯ fly apps list -o personal NAME OWNER STATUS PLATFORM LATEST DEPLOY twumblr personal deployed machines 2023-05-26T01:47:41Z ❯...

3. Setting the FLY_ORG env var did not replace -o in org-level flyctl commands (e.g. fly apps list -o personal). This was a bug in flyctl v0.1.83; a fix was merged and confirmed by the maintainer. Upgrade flyctl to the latest version (fly version upgrade) and FLY_ORG will be respected by org-level commands.

## When to use

You are seeing this: According to @michaeldwan, this is a bug: https://community.fly.io/t/flyctl-feature-request-fly-org-env-var/15099/4. Use this skill when you run into "FLY_ORG is not respected by org-level commands".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

Versions mentioned in the source: fly v0.1.83. If you are on something much newer or older, the details may have shifted.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

## Sources

- https://community.fly.io/t/flyctl-feature-request-fly-org-env-var/15099/4

In the GitHub issue gh:superfly/flyctl#2757 (https://github.com/superfly/flyctl/issues/2757), the problem reported was: Issue superfly/flyctl#2757 (closed, 8 comments): Describe the bug Briefly, describe what broke and provide the following details: Setting the FLYORG env var does not replace -o in org-level commands. According to @michaeldwan, this is a bug: https://community.fly.io/t/flyctl-feature-request-fly-org-env-var/15099/4. Operating system fly version `` fly v0.1.83 darwin/arm64 Commit: 64d1ddb772751c502a038458af4f93fcc9d6a199-dirty BuildDate: 2023-08-22T21:14:46Z ** Command output: ** ``text ❯ fly apps list -o personal NAME OWNER STATUS PLATFORM LATEST DEPLOY twumblr personal deployed machines 2023-05-26T01:47:41Z ❯... The verified resolution was: Setting the FLYORG env var did not replace -o in org-level flyctl commands (e.g. fly apps list -o personal). This was a bug in flyctl v0.1.83; a fix was merged and confirmed by the maintainer. Upgrade flyctl to the latest version (fly version upgrade) and FLY_ORG will be respected by org-level commands.