New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

St2chatops service does not read from environment variables #163

Closed

sahilsk opened this issue Dec 7, 2018 · 1 comment

sahilsk commented Dec 7, 2018

Describe the problem

st2chatops service not honoring environment variables.

** Reproduce **

have hubot enviornment variables set in docker-compose file using env-file
login inside container and empty chatops/st2chatops.env file.
ConfirmEnvironment variables are set:

root@8708d935768e:/opt/stackstorm# echo $HUBOT_ADAPTER
slack

start chatops service sudo service st2chatops restart

** Error **

tail -f /var/log/st2/st2chatops.log

Must provide HUBOT_ADAPTER ENV variable to start.
See README.md for more information
Must provide HUBOT_ADAPTER ENV variable to start.

The text was updated successfully, but these errors were encountered:

lingfish commented Feb 16, 2019

Agreed, same for me. I've had to use bind mount, but this issue means I can't set things like webui_base_url.

warrenvw mentioned this issue

Update docs on how to configure st2chatops #174

Merged

arm4b closed this as completed in

6cc70fd

transhapHigsn pushed a commit to DiligenceVault/st2-docker that referenced this issue


          Remove ALL-IN-ONE Docker deployment

ca5e3eb

You can find the old deprecated version in `DEPRECATED/all-in-one` branch archive: https://github.com/StackStorm/st2-docker/tree/DEPRECATED/all-in-one

Closes StackStorm#22, closes StackStorm#23, closes StackStorm#26, closes StackStorm#29, closes StackStorm#34, closes StackStorm#41, closes StackStorm#43, closes StackStorm#92, closes StackStorm#112, closes StackStorm#117, closes StackStorm#125, closes StackStorm#133, closes StackStorm#141, closes StackStorm#145, closes StackStorm#151, closes StackStorm#163, closes StackStorm#187,
closes StackStorm#188, closes StackStorm#189, closes StackStorm#190
Closes StackStorm#162, closes StackStorm#138, closes StackStorm#108, closes StackStorm#102, closes StackStorm#65

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment