Bug: crash when thing in state no longer exists instead of reporting them as changed outside terraform

[drdamour]

for quite a few resources i've noticed that if the state thinks there's a thing with id 1234 and the anypoint service doesn't see a 1234 i get an error and the plan/apply fail.

this is pretty different than other terraform providers, which report this as a thing that changed outside of terraform and then plan to recreate the resource. It would be better if this provider behaved that way such that in the plan output section about things changed ouside terraform would report these things as destroyed and the plan would show it intends to recreate the the resource

effected resources: business groups, teams, connected apps

the current woraround i have to terraform state rm each resource that the provider thinks/assumes should be there

[soufi]

@drdamour, some new enhancements are on the way with the new version. it's taking more time than expected because we lacking testers. you can pull the dev branch to test the latest changes

[soufi]

is this is still an issue @drdamour ?