LiteFS Cloud token

1

Is it possible to remove the FlyV1 prefix from the LiteFS Cloud token? It would be beneficial to avoid any trouble.

2

It’s currently required for our token versioning on the backend, however, we’re investigating using token aliases to shorten the tokens significantly. We may be able to remove the versioning then.

3

It doesn’t work using it with the secret LITEFS_CLOUD_TOKEN. I would suggest removing it from the UI. That way, the UX will be better.

4

Are you referring to this?

If you quote that substitution like so it should work I would think - does it not?

fly secrets set LITEFS_CLOUD_TOKEN="$(litefs cloud auth token)"
5

lite-fs-cluster-token

My case:

  • I went to LiteFS Cloud
  • I created a new LiteFS Cloud Cluster
  • A new token was provided
  • The “token” had the prefix "FlyV1 "
  • I copied the whole text
  • The token wasn’t valid
  • I had to guess it was because of the prefix
  • I removed the prefix, and it worked

The result was a bad user experience.

6

@gcv I’m surprised it worked without the prefix. It should be required. When you set the secret, did you wrap the entire value in double quotes? e.g.

fly secrets set LITEFS_CLOUD_TOKEN="FlyV1 fm1r_..."
7

I didn’t wrap it. I guess if the cluster shows the databases, it means it is working, isn’t it?

8

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