feat: improve PD service time window validation to accept 86400 as a valid value

[boneff]

Aims to fix: #849

[imjaroiswebdev]

Hi @boneff thank you for your contribution, is a quite complete PR, which also includes the necessary acceptance tests. We appreciate it. However this input value is not currently supported by pagerduty_service.alert_grouping_parameters.0.config.0.time_window as I stated here.

Therefore, I'm proceeding to close this PR for the moment, if the input range gets updated to support what this PR is aiming to add, then We'll considere it as an update to bring support for the new input range.

[imjaroiswebdev]

Hi @boneff you were right about this update, because when I reviewed this improvement, I checked the valid input range for Intelligent Alert Grouping, which is limited to 3600 max. However, this update targets Content Based Alert Grouping input range, which indeed supports 300 <= time_window <= 3600 or 86400(i.e. 24 hours).

So, I'm reopening and reviewing it again. Sorry for the mixup btw 😓

[imjaroiswebdev]

Thank you adding this improvement @boneff. I took the liberty of rebasing and updating the documentation.

[boneff]

Thank you adding this improvement @boneff. I took the liberty of rebasing and updating the documentation.

Thank you for reconsidering @imjaroiswebdev!
Any idea when that change would be released ?

[imjaroiswebdev]

Hi @boneff is already available in version latest version of PagerDuty TF provider, it was released more precisely in version v3.14.0