This repository has been archived by the owner on Oct 30, 2020. It is now read-only.

validator: Validate dynosize in config #99

Open

jonnor opened this issue Mar 14, 2016 · 1 comment

Labels

Milestone

Member

jonnor commented Mar 14, 2016

Can/should use the heroku executable, like we do for config changes, to avoid API key issues

jonnor added the enhancement label

jonnor added this to the 0.2 milestone

jonnor mentioned this issue

NewRelic: Also report dynosize in GuvScaled event #100

Open

Member Author

jonnor commented Oct 6, 2016

Two steps here> 1) check that dynosize string is a valid one. 2) check that the dynosize in config matches that actually deployed.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.