Hey @jacobsmith this looks good. 👍

Can you post a message of how the status message is supposed to look like (especially if both the environments have issues).

I'll then just check it out and merge the PR :)

Yeah, I'd be happy to! I'm having a little bit of trouble being able to run this locally (I usually am working with single-script packages, so just copying the command.coffee file to scripts/ works fine, or I'm just calling out to it in the external-scripts.json file). Mind giving me some pointers?

I've gone to my hubot-heroku repo and run npm link, then gone to my hubot repo and run npm link hubot-heroku -- I'm betting there's some way I need to tell hubot to load the hubot-heroku module, but I cannot seem to figure it out! Any direction would be much appreciated! (:

UPDATE: Okay, I think I figured it out -- I needed to add the node module as a dependency inside of external-scripts.json, but name it as just the package name ( hubot-heroku ). That seems a bit counterintuitive, as I would expect the ...-scripts.json file to be a collection of scripts, not scripts OR modules, but that is a problem with Hubot naming conventions, certainly not this repo! I'll post when I've got the returned text and formatting!

Any luck with the text output? Don't mean to rush, just because this is close to ing. Don't want to be a blocker :)

For context, reason why I asked for the text is so that we can compare the text output you envisioned with tests on the end platforms, I test on Slack and Flowdock, to see if they all look the same / look good.

I actually hit a blocker where I'm getting a 404 when I try and call
heroku.get('/current-status'), so I'm betting the actual URL it is
creating is not completely correct? It might be that most of the
heroku.get methods are actually trying to use the private APIs that need
authentication, and this might be the only public URL. I'm going to try
using just regular robot.http.get('https://HEROKU_API_STATUS') and see if
that gets us any closer -- I'll keep you posted on the progress!

On Fri, Feb 19, 2016 at 12:26 AM, Damon Aw [email protected] wrote:

Any luck with the text output? Don't mean to rush, just because this is
close to [image: ]ing. Don't want to be a blocker :)

For context, reason why I asked for the text is so that we can compare the
text output you envisioned with tests on the end platforms, I test on Slack
and Flowdock, to see if they all look the same / look good.

—
Reply to this email directly or view it on GitHub
#27 (comment).

I'm going to close this as it's 2 years old and I'm not even sure if I still have the code on my computer! Sorry for the clutter! If anyone finds this in the future, feel free to use this work as a starting point (: