Currently, running flagsmith init against an old server results in an obscure error:
➜ dev flagsmith init --api-url <some-url>
Error: <some-url>/.well-known/oauth-authorization-server returned 404 Not Found — is this a Flagsmith API URL?
We should add a server /version check to flagsmith init. If it's less than v2.255.0, friendly nudge the user towards a Master API Key.
The nudge must name the host-scoped variable for the instance, e.g. FLAGSMITH_API_KEY_flagsmith_example_com — anyone hitting this is by definition self-hosted, and the unscoped FLAGSMITH_API_KEY is ignored anywhere but api.flagsmith.com. See #77.
Currently, running
flagsmith initagainst an old server results in an obscure error:We should add a server
/versioncheck toflagsmith init. If it's less than v2.255.0, friendly nudge the user towards a Master API Key.The nudge must name the host-scoped variable for the instance, e.g.
FLAGSMITH_API_KEY_flagsmith_example_com— anyone hitting this is by definition self-hosted, and the unscopedFLAGSMITH_API_KEYis ignored anywhere butapi.flagsmith.com. See #77.