[HRM] SOS API change for VCF 5.2 - Support for VCF 5.2

[bhumitra]

Code of Conduct

• [X] I have read and agree to the project's Code of Conduct.
• [X] Vote on this issue by adding a 👍 reaction to the original issue initial description to help the maintainers prioritize.
• [X] Do not leave "+1" or other comments that do not add relevant information or questions.
• [X] If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Description

Description

New API parameters for VCF 5.2 -

    "healthChecks": {
        "certificateHealth": false,
        "computeHealth": false,
        "connectivityHealth": false,
        "dnsHealth": false,
        "generalHealth": false,
        "hardwareCompatibilityHealth": false,
        "ntpHealth": false,
        "passwordHealth": false,
        "servicesHealth": false,
        "storageHealth": false,
        "versionHealth": false
    },
    "options": {
        "config": {
            "force": false,
            "skipKnownHostCheck": false
        },
        "include": {
            "precheckReport": false,
            "summaryReport": false
        }
    },
    "scope": {
        "domains": [ {
            "clusterNames": [ "" ],
            "domainName": ""
        } ],
        "includeAllDomains": false,
        "includeFreeHosts": false
    }
}

Old payload

Current payload doesnt work with 5.2 and change is needed to support VCF 5.2

Code that needs change is here - https://github.com/vmware/powershell-module-for-vmware-cloud-foundation-reporting/blob/8a7eb5dcb038dabf2e627b14c69aee79a2ed981e/VMware.CloudFoundation.Reporting.psm1#L990

Use Case(s)

See desc

Potential Configuration

No response

References

No response

[bhumitra]

Version 2.2 will fix it.