Mars Hall

Here's a comparison of [my changes thus far](https://github.com/terraform-providers/terraform-provider-heroku/compare/master...mars:buildpack-registry-names). …and here's the relevant output from the new test [`TestAccHerokuBuild_BuildpackRegistryName`](https://github.com/mars/terraform-provider-heroku/blob/5c9dd60de09db8b003e0846bd93fe5e6f7861744/heroku/resource_heroku_build_test.go#L36): ``` buildpacks.0: "https://buildpack-registry.s3.amazonaws.com/buildpacks/heroku/ruby.tgz" => "heroku/ruby" (forces new resource) ```

@sigmavirus24, per my comment above: > Definitely open to ideas here, but I don't think we'll be able to cleanly support Buildpack Registry Names because of this state churn. 🙅‍♂️...

That's a great point @sigmavirus24 👍 If the API call made by `heroku buildpacks -a sushi` returns the correct translation, then it's possible that the provider could be updated to...

That's enlightening @sigmavirus24, that the API doesn't return a clean translation into the names. It looks like there's a pattern that could be matched to translate into a buildpack's Registry...

While I agree that this behavior seems wrong, it's not the whole story. **Heroku config vars are all strings. There are no other types.** So, it seems that the provider...

This is definitely a bug 🐞buuuuut if you try removing the existing formation from state and then re-apply, does it get past this? ``` terraform state rm heroku_formation.app terraform plan...

Hi @chdsbd 😄 > Importing a postgres-db resource should update the config to match the version This is not how `terraform import` works. The HCL config must already match the...

This provider only supports features available in the GA (generally available) [Heroku Platform API](https://devcenter.heroku.com/articles/platform-api-reference). Unfortunately, the API used by the CLI & Dashboard to manage this feature is not part...

Following-up on my 1. above, Remy Sharp just published a fantastic post about this topic: 👓 **[An Adventure in Sparse Arrays](https://remysharp.com/2018/06/26/an-adventure-in-sparse-arrays)**

`heroku_build` resource has nothing to do with how config vars are populated into the build process' `ENV_DIR`. Anecdotally, we have numerous uses of config vars in source-based builds with Terraform,...