Citizen module publish execution requires extraneous ENV variables - Citizen v0.6.0

[abourget-cainc]

Observed when running v0.6.0 cli to publish a module as:

citizen module -v testmod testmod aws 0.0.1

The cli would throw and error if any of the following ENVs are not set:

CITIZEN_DATABASE_TYPE=mysql
CITIZEN_STORAGE=s3
CITIZEN_ADDR=https://registry.address.com/

Obviously the CITIZEN_ADDR needs to be specified, but the other ENV vars are server mode specific. It looks like this was introduced in v0.6.0 with these exception blocks:

citizen/storages/storage.js

Line 12 in 7e4d264

throw new Error(`unknown storage type: ${t}. Please set CITIZEN_STORAGE environment variable.`);

citizen/stores/store.js

Line 14 in 7e4d264

throw new Error(`unknown database type: ${t}. Please set CITIZEN_DATABASE_TYPE environment variable.`);

I was able to work around this by adding conditional logic to only throw the exceptions when running in server mode, and ignoring that block when running module/provider mode.