The beam init command has a --save-to-file command that is opt-in, but we want to change it so that it becomes the default behaviour. Instead, there should be a flag, --no-token-save that prevents the token from saving to disk.
Bug:
With the latest CLI, follow the steps:
Create a new folder and execute beam init --host=dev in the CLI inside it
After loging in with your credentials, create a new service by executing beam project new service <NAME>
Try running the service by executing beam project run --ids <NAME>
Observe that an error related to a refresh token will happen
Execute echo $BEAM_ENV in the CLI
Observe that it's empty
The variable $BEAM_ENV should have all the data necessary for the microservice to be able to run. This is probably the reason why errors are happening when trying to run SAMS.
The
beam init
command has a--save-to-file
command that is opt-in, but we want to change it so that it becomes the default behaviour. Instead, there should be a flag,--no-token-save
that prevents the token from saving to disk.Bug:
With the latest CLI, follow the steps:
beam init --host=dev
in the CLI inside itbeam project new service <NAME>
beam project run --ids <NAME>
echo $BEAM_ENV
in the CLIThe variable
$BEAM_ENV
should have all the data necessary for the microservice to be able to run. This is probably the reason why errors are happening when trying to run SAMS.