Allow specific dynos to be restarted and viewing of dyno list and status #16
Conversation
Allows for the following types of commands: - `hubot heroku restart my-app` (restarts all dynos on app) - `hubot heroku restart my-app worker` (restarts all worker dynos) - `hubot heroku restart my-app web.2` (restarts only the web.2 dyno)
|
@daemonsy let me know your thoughts! |
|
@daemonsy, added tests. should be good to go. |
| @@ -11,7 +11,7 @@ | |||
| # hubot heroku info <app> - Returns useful information about the app | |||
| # hubot heroku releases <app> - Latest 10 releases | |||
| # hubot heroku rollback <app> <version> - Rollback to a release | |||
| # hubot heroku restart <app> - Restarts the app | |||
| # hubot heroku restart <app> <dyno> - Restarts the specified app or dyno/s | |||
There was a problem hiding this comment.
Hey, thanks for this! It makes sense to do this plus some other commands
- Check what's the dyno formation for an app
- Scale web / worker dynos for an app
How about or or here? I haven't had a chance to look into the platform API yet, how do we specify the dyno to be reset? Is it a name or some id? I think it's nice to hint the format in the help message too.
chaselee
changed the title
|
@daemonsy added another command (w/tests) to get the dyno list. Exactly mimics the Heroku cli |
|
Example output for Damon: Dynos of shield-global-watch === worker (2X): |
|
any thoughts @daemonsy? |
|
👍 Thanks for this, it looks good to me. Merging it and releasing after doing a test internally 😄 |
Allow specific dynos to be restarted and viewing of dyno list and status
Allows for the following types of commands:
hubot heroku restart my-app(restarts all dynos on app)hubot heroku restart my-app worker(restarts all worker dynos)hubot heroku restart my-app web.2(restarts only the web.2 dyno)