Mars Hall

I agree, but cannot fix this issue without Heroku API itself making more of these features available. 😞 Thanks for opening this issue, and for your understanding.

Review Apps in a Pipeline are designed to work through Heroku's web dashboard, driven by events from the connected GitHub repo. Using Terraform for this may not be worth the...

You cannot just use Heroku CD with Terraform. There is no provision by Heroku for Terraform intersecting with the built-in developer experience. Either pick Heroku CD, or develop everything using...

@amatellanes please upgrade to the most recent Heroku provider version, [`v5.1.1`](https://github.com/heroku/terraform-provider-heroku/releases/tag/v5.1.1), and let us know if this is still an issue. Note that upgrading from v4 to v5 will require...

Please, see the [updated] explanation on #343. Hopeful it resolves this issue 🙏 CI is failing on some unrelated error, but in the meantime I released [v5.1.4-pre1](https://github.com/heroku/terraform-provider-heroku/releases/tag/v5.1.4-pre1) to allow y'all...

Great to hear @viki53! My guess about `heroku_pipeline_config_var` being changed in-place, is that perhaps one or more of the vars are populated by a dynamic value that is not known...

Due to the dependency on a Heroku API (& Builds service) change for new authorization path with GitHub API, I strongly doubt this will be fixed in the elegant way...

✅ Using a script like this to populate the `source.path` before Terraform runs is the only way to solve this. More than a workaround, this is the solution. Terraform Cloud...

@laurawadden that error indicates that `/tmp/source_code` does not exist, so you need to fix that to proceed without error.

@levivm Clone the source before running Terraform.