Open equivalentideas opened 7 years ago
How would a user configure this?
Some ideas off the top of my head:
MORPH_CONFIGURATION=[{"slack_webhook_url":"https://hooks.slack.com/services/XXXXXXXXXXXXX","runner":"RightToKnow"}]
MORPH_RightToKnow=https://hooks.slack.com/services/XXXXXXXXXXXXX
Some ideas off the top of my head
Nice 👍 I recon an environment variable per runner would be easier for people to manage and add to over time without worrying about messing up existing configuration.
Environment-variable-per-runner makes sense.
If we combine this with #13, the configuration might look something like this:
MORPH_RUNNERS=RightToKnow,PlanningAlerts
MORPH_RUNNERS_RIGHTTOKNOW_WEBHOOK_URL="https://hooks.slack.com/services/XXXXXXXXXXXXX"
MORPH_RUNNERS_RIGHTTOKNOW_POST_DAY=Wednesday
MORPH_RUNNERS_RIGHTTOKNOW_POST_FREQUENCY=weekly
MORPH_RUNNERS_PLANNINGALERTS_WEBHOOK_URL="https://hooks.slack.com/services/XXXXXXXXXXXXX"
MORPH_RUNNERS_PLANNINGALERTS_POST_DAY=Monday
MORPH_RUNNERS_PLANNINGALERTS_POST_FREQUENCY=weekly
Does this look reasonable @equivalentideas?
At the OpenAustralia Foundation we have Jacaranda posting the our main
#townsquare
room. But it might be nice to have the Right To Know runner also post to our project specific#righttoknow
room. Same with PlanningAlerts.It's good for everyone to find out about what's happening with our projects, but it also makes sense for people who just monitor the project room to find out.
On the other hand, someone could post the message from townsquare into the project specific room, and the multiple bot messages could get annoying.
Seems like a reasonable option to me though, and we can always turn it off if it gets annoying.