Mars Hall
                                            Mars Hall
                                        
                                    Hi @talbright ππ I'd be curious if this is still reproducible, as it appears to be evidence of an incident with the platform API. I agree that adding a special...
Unfortunately the Heroku Data APIs to perform these operations is not GA (generally available). Our policy with this provider is to only use GA, officially documented and maintained Heroku APIs.
That's a clever find @oboxodo π π Those `config` options only effect the add-on at creation, and so are [`forceNew` in the provider schema](https://github.com/heroku/terraform-provider-heroku/blob/v5.1.6/heroku/resource_heroku_addon.go#L62). Meaning that changing that `config.follow` value...
Hi @mjuarez π This issue is a documented limitation of [Terraform Data Sources as dependencies](https://www.terraform.io/docs/configuration/data-sources.html#data-resource-dependencies). The configuration will never converge. For a dev environment this may be fine, but for...
Thatβs an interesting idea @mjuarez , to expose those attributes directly on the Space resource. If we can get that data in a data source, then we should be able...
Hi @robertcnix , Would you please add details (maybe open your own separate issue) about what exactly your Terraform configuration is and how you're getting into this state? Are you...
That is correct @robertcnix , "USER_DATABASE" is the **attachment name**, the app-scoped config var name, configurable-on-create via Heroku CLI (issue #227, draft PR supporting configurable-on-create `heroku_addon.attachment_name` #231), β¦while the `heroku_addon.name`...
@robertcnix It sounds like you're trying to use a pre-existing add-on in a Terraform configuration? Is that the case? There are so many ways this could be solved, I'm really...
Hi @romainPrignon, The reason the Pipeline ID is missing on the initial apply, is because the example config is using a data source to get the pipeline's ID. When a...
Sorry for misleading you @romainPrignon. Looking deeper into this, I am reminded that Pipelines API is limited, and [apparently it cannot be usefully Terraformed from scratch](https://github.com/heroku/terraform-provider-heroku/blob/v4.8.0/heroku/resource_heroku_review_app_config_test.go#L9-L11). Best practice will be...