Token generator doesn't understand `!env` vars

[KazimirPodolski]

1. Have some env vars in your powersync.conf:

   ...
   client_auth:
     jwks:
       keys:
         - alg: HS256
           kty: oct
           k: !env PS_JWT_SECRET
   ...

2. Run token generator for this config:

   (node:1755082) [TAG_RESOLVE_FAILED] YAMLWarning: Unresolved tag: !env at line 59, column 12:
   
           k: !env PS_JWT_SECRET
              ^^^^
   

The token was generated tho, but I have a suspicion it's not correct...

[KazimirPodolski]

Replacing the var with the token just for the generation is not ideal because there are other vars involved too:

(node:1755082) [TAG_RESOLVE_FAILED] YAMLWarning: Unresolved tag: !env at line 14, column 12:

      uri: !env PS_DB_REPLICATION_STRING
           ^^^^

(Use `node --trace-warnings ...` to show where the warning was created)
(node:1755082) [TAG_RESOLVE_FAILED] YAMLWarning: Unresolved tag: !env at line 32, column 8:

  uri: !env PS_DB_STORAGE_STRING
       ^^^^

(node:1755082) [TAG_RESOLVE_FAILED] YAMLWarning: Unresolved tag: !env at line 36, column 7:

port: !env PS_PORT
      ^^^^

(node:1755082) [TAG_RESOLVE_FAILED] YAMLWarning: Unresolved tag: !env at line 59, column 12:

        k: !env PS_JWT_SECRET
           ^^^^

[joshua-journey-apps]

I made a fork that supports loading env vars directly when generating a token.
You can try it like this:

node dist/bin.js generate-token \
  --config ~/path/to/powersync.yaml \
  --sub test-user \
  --env ~/path/to/.env

This will populate all the !env values in your config before token generation.

[KazimirPodolski]

It works, thanks!