Jean Baptiste Favre

Actually, downgrading to provider 1.10.1 release gives the same result: ``` > terraform import pagerduty_service_dependency.grafana_use s_uberproxy PQ4FERM.service.PHSCZD5 pagerduty_service_dependency.grafana_uses_uberproxy: Importing from ID "PQ4FERM.service.PHSCZD5"... pagerduty_service_dependency.grafana_uses_uberproxy: Import prepared! Prepared pagerduty_service_dependency for import pagerduty_service_dependency.grafana_uses_uberproxy:...

With Terraform provider 1.8.0, I don't see a crash, but an API error after 2 minutes: ```An execution plan has been generated and is shown below. Resource actions are indicated...

@stmcallister thanks for the details, sounds logical. But, IMHO, there's a misalignment between PagerDuty API and terraform provider here. Terraform provider makes possible to create a catch-all rule, which is...

@stmcallister any news on this topic ? It would be a very usefull improvement to avoid multiple "apply/import/update/apply" setup

> @jbfavre Sorry for the delay on this! So, you're saying we should include the `catch_all` rule object inside the ruleset definition? That's one solution. Another one would be to...

As discussed during Quaterly Terraform Roundtable, another design is to add the `catch_all` only into `pagerduty_ruleset` block. Using previous example, it could be like: ``` resource "pagerduty_ruleset" "foo" { name...

I second this PR, because it could help to manage user_notifications using Terraform, without having the need to manage users It could be the opportunity to enforce users' notifications rules...

@jjm Run into this issue as well, and am still seing it with latest provider release (v2.2.0). Running the terraform apply with TF_LOG=debug show that API acknowledge resource creation. But...

:wave: Got an answer from PagerDuty support: > We've looked into this and determined that the bug results from Terraform attempting to process the event_rule calls concurrently. We are looking...

Hello @Mark0x01 thanks for you report. You're right, documentation is not really up-to-date. I'm working on TLS support and other improvements. I'll update the documentation accordingly.