Skip to content
This repository has been archived by the owner on Feb 12, 2022. It is now read-only.

mcgranaghan feedback #2

Closed
mmcgrana opened this issue Jul 18, 2012 · 1 comment
Closed

mcgranaghan feedback #2

mmcgrana opened this issue Jul 18, 2012 · 1 comment

Comments

@mmcgrana
Copy link
Contributor

The word "checking" appears on the first line but not on any others:

$ heroku production:check
Checking Cedar... OK
Dyno Redundancy... OK
...

Perhaps to avoid this and for symmetry with other commands:

$ heroku production:check
=== Production check for tasseo-production
Cedar... OK
Dyno redundancy... OK

I failed the database checks but didn't have any databases installed:

$ heroku production:check -a tasseo-production
...
Production Database... Failed
Follower Database... Failed
...

$ heroku addons -a tasseo-production
=== tasseo-production Configured Add-ons
deployhooks:campfire
redistogo:nano
ssl:endpoint

In this case consider:

$ heroku production:check -a tasseo-production
...
Production database... N/A
Follower database... N/A
...

It would be nice to know why my checks failed / how I can fix them. Perhaps:

$ heroku production:check -a tasseo-production
...
Log drains... Failed: no drains found

See https://devcenter.heroku.com/articles/maximizing-availability for information
on production app configuration.

For symmetry with other Heroku client plugins like heroku-anvil and heroku-sudo, consider the name heroku-production-check.


Error handling could use tweaking. The current status:

$ heroku production:check -a shogun
Checking Cedar...  !    You do not have direct access or team access to shogun.

/cc @ddollar on CLI style.

@mmcgrana
Copy link
Contributor Author

These are mostly covered now. Going to close. We can re-open with specifc items if we'd lke.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant