GuardiCoreV2 : Enhancement of Incident Severity Parameter to Prevent Command Failures

[shmuel44]

Related Issues

fixes: link to the issue

Description

• Resolved an issue where commands would fail if the Incident Severity parameter was not set. The solution involved adding a default value of "All" to this parameter.

The problem occurred on line 452, where the code checked if "All" was contained in the severity variable. Since severity was None at that time, it resulted in a TypeError: TypeError: argument of type 'NoneType' is not iterable.

To fix this, I added a default value of "All" to the Incident Severity parameter, aligning it with the existing default value for the Incident Type parameter.

[github-actions]

Coverage Report

File	Stmts	Miss	Cover	Missing
Packs/GuardiCore/Integrations/GuardiCoreV2
GuardiCoreV2.py	292	82	71%	93, 171–179, 181–182, 189–192, 194, 196, 204, 209–212, 216–219, 230, 232, 309–310, 325, 337, 367, 373–374, 407, 409, 441–448, 451–466, 468–474, 486–495, 497, 500–501
TOTAL	292	82	71%

Tests	Skipped	Failures	Errors	Time
30	0 💤	0 ❌	0 🔥	2.450s ⏱️

[BEAdi]

Looks great

[talihaff]

@shmuel44 docs approved

[content-bot]

Validate summary
The following errors were thrown as a part of this pr: .
If the AG100 validation in the pre-commit GitHub Action fails, the pull request cannot be force-merged.

Verdict: PR can be force merged from validate perspective? ✅