feat: add support for CIM v5.3.2

[harshilgajera-crest]

Added support for cim v5.3.2.

• Updated data-models with new child data set in various models.
• Updated required fields with updated values as per v5.3.2.
• Added optional fields as per v5.3.2

Detailed comparison and analysis between v4.15.0 and v5.3.2 can be found here: https://docs.google.com/spreadsheets/d/1ZFDC0Efn-bHvcU1Qy78s95GCfWyxt6IUhTv94j3yagk/edit#gid=1147250948

[artemrys]

Can you please double check if this is provided by A&I framework (similar to fields in https://github.com/splunk/pytest-splunk-addon/blob/3ee0404aa07cd56ee67063c4c86aaeaeb3dbb7be/pytest_splunk_addon/standard_lib/cim_tests/CommonFields.json)?

[harshilgajera-crest]

dest_type is not provided by A&I framework, so all fields in https://github.com/splunk/pytest-splunk-addon/blob/3ee0404aa07cd56ee67063c4c86aaeaeb3dbb7be/pytest_splunk_addon/standard_lib/cim_tests/CommonFields.json have the same in description if they are provided by A&I or not.

[justin-splunk]

this is supposed to be the literal string the vendor uses in the log so there no constraint on what may be present.

[harshilgajera-crest]

So we mark it as optional? @justin-splunk
or keep it required but not keep the condition?

[alexeisuv]

The result provides the reason of the action's failure, so I suggest:

• if the status=failure, then the result is required (yes it may not always be present in the raw, but it will prompt the SME to investigate why the action failed - directly from the raw or indirectly from the vendor docs).
• if the status=success, the result is optional.

Is this the current logic?

[harshilgajera-crest]

@alexeisuv
So current condition is that if status=failure then result should be required, else it is optional

[srv-rr-github-token]

🎉 This PR is included in version 5.3.0-beta.6 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[srv-rr-github-token]

🎉 This issue has been resolved in version 5.4.0-beta.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀