-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor: update Request-SoSHealthJson
to use the api
#102
refactor: update Request-SoSHealthJson
to use the api
#102
Conversation
refact: Transition SoS Health to /v1/system/health-summary API change function SoSHealthJson to use REST API for SoS Health calls saved old function SoSHealthJson to SoSHealthJsonOld for backward compatibility Signed-off-by: Kevin Teng <[email protected]>
/v1/system/health-summary
api
Is there a reason why we have not used PowerVCF for the API calls for SoS? |
Great point, Gary! |
I will look into it. |
address all current comments Signed-off-by: Kevin Teng <[email protected]>
@garlicNova, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding
|
8f18bd5
to
af36fbc
Compare
@garlicNova, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding
|
Signed-off-by: Ryan Johnson <[email protected]>
af36fbc
to
df50db0
Compare
Adds a workload domain example to the refactored `Request-SoSHealthJson` cmdlet. Signed-off-by: Ryan Johnson <[email protected]>
Signed-off-by: Ryan Johnson <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Error observered on VMware Photon OS with PowerShell Core:
PS /home/vmware/code/VMware.CloudFoundation.Reporting> Import-Module ./VMware.CloudFoundation.Reporting.psm1 PS /home/vmware/code/VMware.CloudFoundation.Reporting> Request-SoSHealthJson -server sfo-vcf01.sfo.rainpole.io -user admin@local -pass VMw@re1!VMw@re1! -reportPath /home/vmware/reports -workloadDomain sfo-w01
tar (child): /home/vmware/reports\\1I1K3C\\health-summary.tar.gz: Cannot open: No such file or directory ]
tar (child): Error is not recoverable: exiting now
/usr/bin/tar: Child returned status 2
Copy-Item: Cannot find path '/health-results.json' because it does not exist.
Get-Content: Cannot find path '/home/vmware/reports/sfo-w01-all-health-results.json' because it does not exist.
/home/vmware/reports/sfo-w01-all-health-results.json
fix error on linux path / vs \ Signed-off-by: Kevin Teng <[email protected]>
fixed, change hardcode path "backward slash" to use powershell cmdlets Join-Path to resolve issues between windows and linux. (backward slash vs forward slash) |
- Updates the version from v1.1.0 to v2.0.0 for next release milestone. - Updates the GUID for the next release milestone. - Updates the module description for the next release milestone. - Updates the generated date to current; to be updated for the next release milestone. Signed-off-by: Ryan Johnson <[email protected]>
Updates `CHANGELOG.md`. Signed-off-by: Ryan Johnson <[email protected]>
27d6c8d
to
7613418
Compare
/v1/system/health-summary
apiRequest-SoSHealthJson
to use the api
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. |
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
Transition SoS Health to
/v1/system/health-summary
API.Signed-off-by: Kevin Teng [email protected]
Type of Pull Request
Please describe:
Related to Existing Issues
Closes #96
Test and Documentation Coverage
Breaking Changes?
Breaks the use of
Publish-LocalUserExpiry
when running the health report. This will be resolved in #90 which must be completed for v2.0.0 to usePublish-PasswordHealth
.