Is your feature request related to a problem? Please describe.
At present when running quant init commands a user needs to manually retrieve and provide project values.
This is inefficient and requires manual config retrieval via the UI/Dashboard.
Describe the solution you'd like
A user can authenticate with a new quant login command and an auth token is generated and stored locally. From this point on project config values can be pulled on demand, for example
quant init
*** Select a project **
> project-a
project-b
project-c
New project
As per the above this also allows project creation on demand too, rather than the back and forth required via the UI at present.
Is your feature request related to a problem? Please describe.
At present when running
quant initcommands a user needs to manually retrieve and provide project values.This is inefficient and requires manual config retrieval via the UI/Dashboard.
Describe the solution you'd like
A user can authenticate with a new
quant logincommand and an auth token is generated and stored locally. From this point on project config values can be pulled on demand, for exampleAs per the above this also allows project creation on demand too, rather than the back and forth required via the UI at present.