feat: update Publish-* methods for JSON generation

[bhumitra]

In order to have a good experience with our community, we recommend that you read the contributing guidelines for making a pull request.

Summary of Pull Request

Updated Publish-* cmdlets to support JSON generation for:

• Publish-BackupStatus
• Publish-NsxtTransportNodeStatus
• Publish-NsxtTier0BgpStatus
• Publish-SnapshotStatus
• Publish-LocalUserExpiry
• Publish-StorageCapacityHealth

Added 2 additional functions:

• Publish-NsxtHealthNonSOS
• Publish-ComponentConnectivityHealthNonSOS

Signed-off-by: bhumitra nagar bnagar@vmware.com

Type of Pull Request

• This is a bug fix.
• This is an enhancement or feature.
• This is a code style / formatting update.
• This is a documentation update.
• This is a refactoring update.
• This is a chore update
• This is something else.
  Please describe:

Related to Existing Issues

Closes #37

Test and Documentation Coverage

• Tests have been completed (for bug fixes / features).
• Documentation has been added / updated (for bug fixes / features).

Breaking Changes?

• Yes, there are breaking changes.
• No, there are no breaking changes.

New if/else path has been added to these cmdlets. if called using -jsonOutput, then JSON is generated. Else, the functionality is the same as before. I have tested the functionality and it works fine.

[tenthirtyam]

Hi @bhumitra -

I’ve marked the pull request for the v1.1.0 milestone release planned for February 2023. We will hold the merging of this pull request until after the v1.0.6 milestone release for January 2023. Reviews will, however, occur soon. 🚀

Ryan Johnson
Senior Staff Solutions Architect | Product Engineering @ VMware, Inc.

[tenthirtyam]

Update: I will review it soon now that v1.0.6 is now released.

[tenthirtyam]

Minor changes requestion on first pass:

• Other examples and the README.md use F:\Reporting vs F:\Reports. Added suggestions to keep them consistent.
• Use -Depth vs -depth.
• Minor grammatical suggestions.

[tenthirtyam]

Thanks for committing the review suggestions.

I’ll give in a flurry of tests tomorrow and report back.

[tenthirtyam]

LGTM! 🚀

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.