Provider should be resilient to resources not found

[dstendardi-booksy]

Description

According to the terraform recommendation, a provider should :

Ignore errors that signify the resource is no longer existent.

However this happens with protocol transformations (but not only)

 Error: Unable to read Transformation (ID: 2uorPuhgzltxsQ6uNd0bYbulr0S)
  │ 
  │   with segment_transformation.rename_events["mysource"],
  │   on segment.tf line 187, in resource "segment_transformation" "rename_events":
  │  187: resource "segment_transformation" "rename_events" {
  │ 
  │ 404 Not Found
  │ {
  │   "errors": [
  │     {
  │       "type": "not-found",
  │       "message": "Transformation with id 'xxx' not found"
  │     }
  │   ]
  │ }
  ╵

To Reproduce

• create a transformation with protocol
• apply
• delete the transformation in the ui
• plan again

[deanhuynh]

This should be fixed in v1.4.0 let me know if you run into any other issues!

[dstendardi-booksy]

thank you dean !