VaronisSaaS: add 'Informational' alert severity; bump pack to 1.0.14 and add release notes

[bdudnyk-varonis]

add support for "Informational" severity when fetching and filtering alerts

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

:white_check_mark: vkorenkov-varonis
:x: bdudnyk-varonis
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[content-bot]

Thank you for your contribution. Your generosity and caring are unrivaled! Make sure to register your contribution by filling the Contribution Registration form, so our content wizard @merit-maita will know the proposed changes are ready to be reviewed. For your convenience, here is a link to the contributions SLAs document.

[content-bot]

Hi @bdudnyk-varonis, thanks for contributing to the XSOAR marketplace. To receive credit for your generous contribution please follow this link.

[bdudnyk-varonis]

Hi @bdudnyk-varonis, thank you for your contribution! It looks like two version bumps were added, bringing the pack to 1.0.14 instead of introducing a single version update. Was this intentional?

After version 1.0.12 I know we had one change (to 1.0.13) from previous developer: https://github.com/demisto/content/pull/40305/files

which was reviewed and approved. But I saw it merged only to his fork (https://github.com/vkorenkov-varonis/content/tree/varonis-dev) but not to master https://github.com/demisto/content. I'll try to contact the dev vkorenkov-varonis who worked on this. But I believe we don't want to lose these changes (1.0.12 -> 1.0.13) so this was the reason why I branched from this fork (not from master) to add new changes.

Regarding the changes to the existing incident field: modifying its values is not allowed, as it can break compatibility for current customers. If these updates are required, I recommend creating a new incident field with the updated values instead.

For the change that I did now (1.0.13->1.0.14) I just added new allowed value (for alert severity) w/o changing/removing existing values. Here is commit: https://github.com/demisto/content/commit/3c5f2db710f05462fab56fe1d5dcfd2b8d5a3fd9.

And I think it should not break compatibility for current customers.

So could you pls clarify if your note about modifying values was related to this change: https://github.com/demisto/content/pull/40305/files (1.0.12 -> 1.0.13) made 6 month ago. It will help me to understand the further actions.

Thanks.

[bdudnyk-varonis]

Hi, @Benimanela, continuing the previous comment: we'd like to merge first this PR https://github.com/demisto/content/pull/40305/files (1.0.12 -> 1.0.13) which was reviewed and discussed it will not break compatibility for current customers. I don't know the reason why wasn't merged to master but as I understood after the conversation with author - it should be.

So then we can review the actual current change that I'm doing now: (1.0.13->1.0.14) where I just added new allowed value (for alert severity) w/o changing/removing existing values. Here is commit: https://github.com/demisto/content/commit/3c5f2db710f05462fab56fe1d5dcfd2b8d5a3fd9

WDYT? Thanks.