Closed KlavsKlavsen closed 3 years ago
@KlavsKlavsen thanks for reporting this. Invalid adapters config
makes me think there's something wrong with the format of the config, but your env vars look ok at first glance. I'll try to reproduce this.
@devth Anything I can do to help reproduce this? Can I enable "debug output" or something to more information on why its failing? I checked with curl - and it can reach our mattermost just fine
@KlavsKlavsen sorry for the delay!
I figured out what's wrong: the YETIBOT_ENV_PREFIX=yb
config tells it to only load config from env vars prefixed with yb
or YB
, so it was ignoring all your YETIBOT_*
vars.
I use this option specifically when running in Kubernetes, since K8S injects a bunch of YETIBOT_* vars that sometimes conflict with Yetibot's own config.
Fantastic.. I totally should have seen that myself :)
closing - opening new clojail bug in new issue
I've set the following envs:
and get this failure output (in docker/k8s):