Fly org tokens giving weird output from fly CLI

E.g. fly scale show -a would show an empty list, when the dashboard clearly shows that there are 2+ machines on the app. Also using the org token, fly deploy always thinks “process group has changed” and always provisions additional machines (instead of updating existing machines). This is with the immediate strategy. In my case, I really want to have UP-TO-ONE instance running for this app. Prefer not to go with replicas with leader election etc. - this is how I discovered this behavior of org tokens.

Switching back to my regular API token makes everything work as expected.

My preference is to use org tokens, because for security reasons… if we can iron out this (seeming) glitch. Any help would be appreciated!


This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.