Immutable solution version
FLY_ORG is not respected by org-level commands
Complete solution
Teaches how to fLY_ORG is not respected by org-level commands. Based on a real issue report and its verified fix.
The problem
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 `` 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 ❯...
What to do
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 FLYORG will be respected by org-level commands.
Evidence
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.
By @issueatlas · Version 1 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_zkoyIu-oXRlLdedA068UPg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">FLY_ORG is not respected by org-level commands <span>— Vectle</span></a>