Closed joechu1 closed 3 years ago
@joechu1 sorry for the long delay here. I've been working on a sizable update and just got it merged––this should now work as expected with the latest changes.
Manually setting an environmental variable
export STARBURST_LIC_PATH=
That method is currently unsupported. I could add logic to consume already-set shell variables, but we'd need to decide if a shell environment variable should override an existing config if already set in minipresto.cfg
. The only way to pass variables to Minipresto right now is in minipresto.cfg
and the --env
option.
Setting STARBURST_LIC_PATH
in minipresto.cfg
or passing as an --env
option should now work as long as that volume mount is uncommented in your docker-compose.yml
file.
I'm going to close this, but please let me know if you still experience issues.
It doesn't look like the STARBURST_LIC_PATH property in the Minipresto configuration is used when provisioning a cluster. More importantly, once the STARBURST_LIC_PATH property is set and the volume is uncommented in the docker-compose.yml, Minipresto will return an error when provisioning:
So for some reason, STARBURST_LIC_PATH is not set as an environmental variable. Manually setting an environmental variable
export STARBURST_LIC_PATH=
or using the flagminipresto provision --env STARBURST_LIC_PATH=
works as a workaround.Minipresto version - commit 419edb49866c604e6df5dca1e6d7b44aa6d84444
minipresto.cfg
docker-compose.yml