Option to make `heroku_app_config_association` destroy no-op?

[dentarg]

Hi,

I use the provider to set up and tear down apps for an staging environment and I noticed a bit of a gotcha: when I start terraform destroy to remove all my resources heroku_app, heroku_build, heroku_app_config_association and more) it has failed with this message:

╷
│ Error: error waiting for new release (9845a15d-5736-4dee-bd68-47b1f75b542f) to succeed: unexpected state 'failed', wanted target 'succeeded'. last error: %!s(<nil>)
│
│
╵

terraform-provider-heroku/heroku/resource_heroku_app_config_association.go

Lines 180 to 182 in b03a303

	if _, err := stateConf.WaitForState(); err != nil {
	return fmt.Errorf("error waiting for new release (%s) to succeed: %s", releases[0].ID, err)
	}

Sure enough, the build removing all the vars did fail, as that build depend on (some) of the vars.

terraform-provider-heroku/heroku/resource_heroku_app_config_association.go

Lines 141 to 144 in b03a303

	// Essentially execute an update to delete all the vars listed in the schema only
	if err := updateVars(appId, client, allVars, nil); err != nil {
	return err
	}

[dentarg]

My workaround for now is to terraform state rm all heroku_app_config_association before terraform destroy.