Address: pagerduty_service.alert_grouping_parameters.config block parsing

[imjaroiswebdev]

Address #550

This update is aimed to correctly handle the parsing for pagerduty_service.alert_grouping_paramerts.config block.

Test results...

[stmcallister]

Looks good to me! Are there any changes that need to be made to the documentation because of this change?

[imjaroiswebdev]

It's great that you point this out @stmcallister, because the issue being addressed by this PR is happening because the current implementation doesn't stick to the documented API when it has to do with updating pagerduty_service.alert_grouping_parameters configurations, and now with this update the Provider will able to consistently create and update pagerduty_service.alert_grouping_parameters resource configurations.

[davidpellcb]

Hi all, found this PR through various googling. We're currently way behind on our provider version (2.1.1) but seeing constant unnecessary diffs in our plans that look like this for every single service that uses alerting_group_parameters with type = "intelligent":

We see the same issue when testing with 2.6.2.

However, if we actually use config: [] in the alerting_group_parameters we get an error:

I believe this is because config isn't meant to be used with type = "intelligent" based on the docs:

Not sure if this is an issue with the PD API or the TF provider. Also unsure from reading the PR description if this will address our issue. Do I need to open a separate issue?

[imjaroiswebdev]

Hi @davidpellcb the issue you are facing with your config is more related to the syntax, because your are trying to declare an Attribute named config, instead of a config block.