You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Create a new environment variable `EXIT_ON_FAILURES` with default value `false`. If user is not explicitly setup, it will work as today.
If `EXIT_ON_FAILURES` is setup, for the case if `st2chatops` encounters authenticate or unresolved application URL issues with Stackstorm, instead it's being unresponsive/hanging/waiting in a running state, `st2chatops` will be exit.
Copy file name to clipboardExpand all lines: README.md
+1Lines changed: 1 addition & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -77,6 +77,7 @@ specified when running hubot:
77
77
*`ST2_SLACK_FAIL_COLOR` - Slack attachement color for failures either be one of good, warning, danger, or any hex color code (optional).
78
78
*`ST2_ROCKETCHAT_SUCCESS_COLOR` - RocketChat attachement color for success, can either be one of good, warning, danger, or any hex color code (optional).
79
79
*`ST2_ROCKETCHAT_FAIL_COLOR` - RocketChat attachement color for failures either be one of good, warning, danger, or any hex color code (optional).
80
+
*`EXIT_ON_FAILURES` - Exit from st2chatops for st2client failures. Default is `false` (optional).
80
81
81
82
Note: ``ST2_ROUTE`` environment variable mentioned below should only be
82
83
specified if you modified the rule which comes with a ``hubot`` pack to use a
0 commit comments