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
{{ message }}
This repository has been archived by the owner on Feb 12, 2022. It is now read-only.
$ heroku ps -a st-kpi-http-gateway
=== web (Private-L): bin/s3env run bin/cedar kpi-http-gateway-api (4)
web.1: up 2017/11/16 21:10:50 -0800 (~ 16s ago)
web.2: up 2017/11/16 21:02:26 -0800 (~ 8m ago)
web.3: up 2017/11/16 21:03:14 -0800 (~ 7m ago)
web.4: up 2017/11/16 21:03:59 -0800 (~ 7m ago)
It's not obvious from this output that web.1 is running a different release than the other dynos. In this particular case, the app is in a Private Space, and so it'll be a few minutes before all the dynos are on the same release. This can be a bit surprising. I know I could use heroku ps:wait or pass --extended to wait for all the dynos to cycle or see the release version for each one, respectively, but both of those things are non-default behaviour that can be hard to discover or to remember to use.
It'd be nice to show the release in the output of heroku ps:
$ heroku ps -a st-kpi-http-gateway
=== web (Private-L): bin/s3env run bin/cedar kpi-http-gateway-api (4)
web.1: up v1117 2017/11/16 21:10:50 -0800 (~ 16s ago)
web.2: up v1116 2017/11/16 21:02:26 -0800 (~ 8m ago)
web.3: up v1116 2017/11/16 21:03:14 -0800 (~ 7m ago)
web.4: up v1116 2017/11/16 21:03:59 -0800 (~ 7m ago)
The text was updated successfully, but these errors were encountered:
great suggestion @jkakar, we're a little backed up right now but I'll put it on our board to look into. I'm not sure if we have this data from API either, but I'll find out.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
heroku ps
currently shows output like this:It's not obvious from this output that
web.1
is running a different release than the other dynos. In this particular case, the app is in a Private Space, and so it'll be a few minutes before all the dynos are on the same release. This can be a bit surprising. I know I could useheroku ps:wait
or pass--extended
to wait for all the dynos to cycle or see the release version for each one, respectively, but both of those things are non-default behaviour that can be hard to discover or to remember to use.It'd be nice to show the release in the output of
heroku ps
:The text was updated successfully, but these errors were encountered: