Addressing pagerduty_slack_connection unable to set "No Priority" vs "Any Priority" for priorities configuration

[imjaroiswebdev]

Addressing #456

After validating the behaviour of PagerDuty's API in regards of configuring the priorities for Slack Connection resource and comparing it with the current capabilities of our TF Provider, I could make sure that there ware no way to configure a No Priority priorities setting sticking to the interface of the PagerDuty's API. So it was necessary to add a more explicit way to achieve this configuration. As a result We end up making a little upgrade to the priorities attribute interface:

• priorities - (Optional) Allows you to filter events by priority. Needs to be an array of PagerDuty priority IDs. Available through pagerduty_priority data source.
  • When omitted or set to an empty array ([]) in the configuration for a Slack Connection, its default behaviour is to set priorities to No Priority value.
  • When set to ["*"] its corresponding value for priorities in Slack Connection's configuration will be Any Priority.

Test results:

[stmcallister]

Very cool! Love the idea of adding the * syntax! Thank you!! 👍 🌮 🎉

[mrwacky42]

Is it me, or is this a breaking change? It looks like the default value is the opposite of the old default value.

 resource "pagerduty_slack_connection" "slack" {
        id                = "<redacted>"
        # (7 unchanged attributes hidden)

!       config {
!           priorities = [
-               "*",
            ]
            # (1 unchanged attribute hidden)
        }
    }