Ignoring API error for a specific resource


We are experiencing an issue on Google’s side where one of their API consistently fails (today: gke pools in us-central-1c). This prevents us from running plans altogether (on totally unrelated resources).

We were wondering if there was a way to completely ignore the problematic resource.

Ignoring changes in the lifecycle does not prevent the API call from happening.

      lifecycle {
        ignore_changes = all

We could delete the resource and remove it from the state, but it seems quite drastic for a temporary issue.