Allow sending commands to add-ons

[lpender]

I'm a bit baffled by the following set of decisions.

1. Deprecate the heroku gem.
2. Don't install the "Heroku Toolbelt" by default on Heroku instances.

This forces users to use something like the Heroku buildpack: Heroku Toolbelt to run heroku commands on their staging server.

The platform-api provides a partial solution by creating something that can be accessed by a rake task,, but it would be great if it allowed interactions with addons, such as pgbackups or pgextras.

Thanks!
-Lee

[brandur]

This forces users to use something like the Heroku buildpack: Heroku Toolbelt to run heroku commands on their staging server.

Hey Lee, just of curiosity, what kinds of things do you run from your dynos from the CLI?

The platform-api provides a partial solution by creating something that can be accessed by a rake task,, but it would be great if it allowed interactions with addons, such as pgbackups or pgextras.

Certainly a known defect! Unfortunately those two services have lived outside of the main Heroku API since inception. We'd like to get them pulled in to the official API, but we're still working on this objective internally.

[abuisman]

+1 on the pgbackups.

What is the recommended way of getting the 'latest backup' url for a certain app?

[brandur]

@abuisman Pgbackups does have an API which you can see used from with the code in https://github.com/heroku/heroku, and you should be able to procure a backup URL from it. However, this API is not guaranteed to be stable at the moment, so if you wanted to use it, we'd suggest monitoring for breakage.

[lpender]

Hi @brandur!

Thanks for the response!

I was tasked with writing a script to transfer my Production DB to Staging every day.

I ended up using the multi-buildpack.

Thanks!

[dirtyhenry]

+1 on the pgbackups.

[geemus]

closing in favor of #47 (just to reduce duplication a bit)