echo $JUJU_ENV_VARS

[Tim Penhey]

On 05/11/15 07:23, Nick Veitch wrote:
> Greetings.
> 
> For a long time now, the docs have had a list of the environment
> variables used by Juju. It is a single page that is rather useful to
> everyone:
> 
> https://jujucharms.com/docs/stable/reference-environment-variables
> 
> It would be a lot more useful if it was complete, but there are several
> environment variables which are not on the list. It would be incredibly
> useful if you could
> 
>  a) read that page
>  b) check if all the env vars you know of are on the list
>  c) if not, either file an issue [1], reply here, email me or in some
> other way communicate what is missing along with some idea of what it does.

JUJU_DEV_FEATURE_FLAGS, comma separated list of feature names to enable
features under development. Not to be used in production, but gives
users early access to work.

As a side note, there is a flag that is useful for developers to have
all the time: log-error-stack.

>From the comment:

// LogErrorStack is a developer feature flag to have the LoggedErrorStack
// function in the utils package write out the error stack as defined by the
// errors package to the logger.  The ability to log the error stack is very
// useful in those error cases where you really don't expect there to be a
// failure.  This means that the developers with this flag set will see the
// stack trace in the log output, but normal deployments never will.

JUJU_STARTUP_LOGGING_CONFIG is a new (master / 1.26) variable that I
ended up adding to better debug program initialization. Under normal
circumstances the debugging flags are not set until the supercommand
Init method is executed for the CLI. If this environment variable is
set, the logging config is set at module initialization time, before the
main function starts.

Tim