Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Expand --version command

See original GitHub issue

Currently the version command just returns the CLI version and one commit hash for the binary which is hardcoded in the package.json - not the actual hash that the binary returns when asked for it.

Ideally the CLI would request the version from all the binaries version endpoints and output something like this:

prisma2@2.0.0-alpha.473
All binaries are on the same commit : 9sfhshfjdhfjsdhfs....`

Or in the case they differ (due to the usage of env vars to point to local binaries)

prisma2@2.0.0-alpha.473
The binaries are on different commits: 
 Introspection-Engine : 9fadsfsdfsdf...
 Query-Engine : 5j245h45kk2hhgfsfsdf...
 Migration-Engine : 92047254hsfs7s8fs02f...

Issue Analytics

State:
Created 4 years ago
Reactions:1
Comments:6 (6 by maintainers)

Top GitHub Comments

3reactions

timsuchanekcommented, Jan 27, 2020

In addition, we should adjust the --version command, to take into account, if an engine override env var is present. If you e.g. provide PRISMA_QUERY_ENGINE_BINARY, the --version command should print information about the binary that is targeted by that env var, instead of just printing the shipped binary.

2reactions

timsuchanekcommented, Mar 16, 2020

The new output will look as follows:

Prisma CLI Version   : prisma2@2.0.0-alpha.473
Current platform     : darwin
Query Engine         : version (at /.../.../, resolved by PRISMA_QUERY_ENGINE_BINARY)
Migration Engine     : version (at /.../.../)
Introspection Engine : version (at /.../.../)