Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Option to make heroku_app_config_association destroy no-op? #382

Open
dentarg opened this issue Jan 17, 2024 · 1 comment
Open

Option to make heroku_app_config_association destroy no-op? #382

dentarg opened this issue Jan 17, 2024 · 1 comment

Comments

@dentarg
Copy link

dentarg commented Jan 17, 2024

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>)
│
│
╵

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.

// 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
Copy link
Author

dentarg commented Jan 17, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant