/resources endpoint

[will]

Heroku::API is missing the top level /resources endpoint.

I may get around to submitting a patch, but I got my code working with just #request(path: '/resources', method: :get, expects: 200).body so I may forget to do it, so I'm opening this ticket now while thinking about it.

[geemus]

@will - correct. Since resources are not released yet I hadn't gotten around to supporting them yet. Good to know there is a simple way to access them despite this omission. Will definitely make sure they are supported if/when we release this.

[will]

Even if it is never released as a CLI facing endpoint, dataclips uses that
API extensively.

On Friday, December 14, 2012, Wesley Beary wrote:

@will https://github.com/will - correct. Since resources are not
released yet I hadn't gotten around to supporting them yet. Good to know
there is a simple way to access them despite this omission. Will definitely
make sure they are supported if/when we release this.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/35#issuecomment-11384354.

[geemus]

@will - hmm, good to know (I was unaware). How is it making use of this?

[will]

/resources is how dataclips figures out what databases you have access to.
Otherwise it'd have to get your apps then do an API call per app you have.

On Friday, December 14, 2012, Wesley Beary wrote:

@will https://github.com/will - hmm, good to know (I was unaware). How
is it making use of this?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/35#issuecomment-11386447.

[geemus]

@will - Interesting, makes sense. Is this not accessible from our postgres API?

[will]

I'm not sure which postgres api you're referring to, but in each one I can
think of the answer is no. core is the only source of the knowledge because
people can change their api key, email address, app names at any time, and
those changes are not sent out to add-on providers. Furthermore addon
providers have no idea about people collaborated on an app, just the owner.

On Fri, Dec 14, 2012 at 10:29 AM, Wesley Beary [email protected]:

@will https://github.com/will - Interesting, makes sense. Is this not
accessible from our postgres API?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/35#issuecomment-11386773.

[geemus]

@will - fair enough. I guess naively that it seems like the provider of the databases would know about my databases, but I can certainly see how/why this isn't the case (at least currently). Perhaps this data should flow more freely to addon providers or perhaps I just need to be less naive.