Robert C. Nix

@bernerdschaefer Giving the add-on a custom name would also be perfect as long as I can give it the same name as its app and if that name does *not*...

> Re-reading those docs, I see that the custom addon name still needs to be globally unique, but you already mentioned that should work for you since you can use...

@davidji99 I'll test it out within the next few days and update the issue accordingly. Thanks!

@davidji99 Can you help with the usage for `heroku_addon` data resource? All i have access to is the app name, not the add-on name but when i try to use...

This question is pertaining to the add-on's app so it will never have more than one add-on, right? But as a general solution, the way i've used the CLI is...

@mars If i do this to get a handle to an addon, it can't be "USER_DATABASE", right? It's the globally unique name that Heroku generates? data "heroku_addon" "addons" { name...

We have a process where we create add-ons separately from the apps we deploy. For example, imagine an Operations team provides several databases that apps/services can attach and service-developers are...

Basically, this is what I need to be able to do: ``` resource heroku_addon_attachment db_main { addon_id = "my-addon" app_id = data.heroku_app.app.id } data heroku_app app { name = "my-app-name"...

I tested with this version and it seems to function properly: ``` # terraform -v Terraform v0.12.3 + provider.heroku v2.0.1 + provider.local v1.2.2 + provider.null v2.1.2 + provider.vault v2.0.0 ```...

I'm running into this. Any chance we can get this PR fixed and merged? Thanks