Fix: Allow modifying NFS Export with valid zero values

[rounak-adhikary]

PR Submission checklist

GitHub Issues

List the GitHub issues impacted by this PR:

GitHub Issue #
dell/terraform-provider-powerstore#120

Common PR Checklist:

• Have you made sure that the code compiles?
• Have you commented your code, particularly in hard-to-understand areas?
• Did you run tests in a real Kubernetes cluster?
• Have you maintained backward compatibility?
• Have you updated the mocks for any Client functions that have been modified (mocks/Client.go)?

Description of your changes:

Allowing patching NFS Export with valid zero values.
The JSON tag for NFS Owner Username field. Fixed that.

This fix is similar to #184

Tested via

Integration Tests

root@lglap049:~/gopowerstore# go test -run "NFSExport" ./inttests
ok      github.com/dell/gopowerstore/inttests   84.368s
root@lglap049:~/gopowerstore#

[github-actions]

Merging this branch will not change overall coverage

Impacted Packages	Coverage Δ	🤖
github.com/dell/gopowerstore	91.63% (ø)

---

Coverage by file

Changed files (no unit tests)

Changed File	Coverage Δ	Total	Covered	Missed	🤖
github.com/dell/gopowerstore/nfs_types.go	100.00% (ø)	2	2	0

Please note that the "Total", "Covered", and "Missed" counts above refer to code statements instead of lines of code. The value in brackets refers to the test coverage of that file in the old version of the code.

[santhoshatdell]

Hi,
For all the hosts list, there are 'add' and 'remove' lists in NFSExportModify. Could you check if you can make use of those fields to add or remove a host from the list during modify operation.?
Removing omitempty for these lists have an effect on other Client library users.

[santhoshatdell]

I am not sure if one can unset AnonymousUID and GID. If that is not allowed, let's not remove 'omitempty'.