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

terraform error after manually deleting a component from statuspage #36

Closed
ghost opened this issue Jan 27, 2021 · 6 comments
Closed

terraform error after manually deleting a component from statuspage #36

ghost opened this issue Jan 27, 2021 · 6 comments

Comments

@ghost
Copy link

ghost commented Jan 27, 2021

Hello,
This provider does not seem to appreciate when a component is (manually) deleted from statuspage.
After manual deletion, I got:

terraform plan
[...]
Error: could not find component with ID: 9nt3wb5yrbm9, http status 404

I expected for terraform plan to succeed and propose to reprovision the component.

Terraform v0.13.6
+ provider registry.terraform.io/yannh/statuspage v0.1.7
@yannh
Copy link
Owner

yannh commented Jan 27, 2021

Urgh, so would I, thanks for the report ❤️

@yannh
Copy link
Owner

yannh commented Mar 31, 2021

I tried a fix for this - but I have not been able to really write a test for this yet, so I am unsure if this is actually fixed. Writing a test for this is a bit of a challenge, hopefully I'll get back to it soon 👍

@mtaylor-evidation
Copy link

Any updates on this I'm experiencing this issue also.

@yannh
Copy link
Owner

yannh commented May 11, 2022

Fixed in v0.1.12 🙇 It should include such a note now , and make a plan to recreate the resources.
image

@yannh yannh closed this as completed May 11, 2022
@yannh
Copy link
Owner

yannh commented May 11, 2022

Mh reopening since the CI is failing for some reason, though that seems unrelated to this change 🤔

@yannh yannh reopened this May 11, 2022
@yannh
Copy link
Owner

yannh commented May 11, 2022

Fixed and repushed the tag , was linked to hashicorp/hc-install#59 - it's really quite bad that they did not manage to make this change backward compatible, all providers might fail to build now, and it will be potentially impossible to rebuild older versions of any providers without change.

@yannh yannh closed this as completed May 11, 2022
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

2 participants