-
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
feat: adjust thresholds for certificate health #107
feat: adjust thresholds for certificate health #107
Conversation
Signed-off-by: bhumitra nagar <[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.
LGTM! 🚀
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 observed on Windows:
PS F:\VMware.CloudFoundation.Reporting> Import-Module .\VMware.CloudFoundation.Reporting.psd1
PS F:\VMware.CloudFoundation.Reporting> Publish-CertificateHealth -json F:\Reporting\HealthReports\sfo-w01-all-health-results.json
[03-28-2023_14:17:05] Error at Script Line 926
[03-28-2023_14:17:05] Relevant Command: $expiry = [DateTime]::ParseExact($element.title[2], "MMM dd HH:mm:ss yyyy 'GMT'", $null).ToUniversalTime()
[03-28-2023_14:17:05] Error Message: Exception calling "ParseExact" with "3" argument(s): "String was not recognized as a valid DateTime."
PS F:\VMware.CloudFoundation.Reporting> Publish-CertificateHealth -json F:\Reporting\HealthReports\sfo-vcf01-all-health-results.json
[03-28-2023_14:17:22] Error at Script Line 926
[03-28-2023_14:17:22] Relevant Command: $expiry = [DateTime]::ParseExact($element.title[2], "MMM dd HH:mm:ss yyyy 'GMT'", $null).ToUniversalTime()
[03-28-2023_14:17:22] Error Message: Exception calling "ParseExact" with "3" argument(s): "String was not recognized as a valid DateTime."
Marked as draft whilst awaiting changes. |
Signed-off-by: bhumitra nagar <[email protected]>
Looks good after testing with the update but I do see an oddity where it’s reporting a -25 but an 8 day expiration. You can test with the JSON I provided over Slack. I suspect this is a data issue from SoS? PS F:\VMware.CloudFoundation.Reporting> Publish-CertificateHealth -json F:\Reporting\HealthReports\sfo-vcf01-all-health-results.json -failureOnly
Component : vRLI
Resource : sfo-vrli01a.sfo.rainpole.io
Expires In (Days) : -25
Alert : RED
Message : Certificate validation is failed for vRLI:sfo-vrli01a.sfo.rainpole.io. If Certificate End date is 15 days or less, SoS will show result as failed.Certificate expires in 8
day(s). |
I’ll submit an update for the build and changelog before merge. |
@bhumitra, 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]>
c53b7a6
to
349b76f
Compare
Bumps the module version to v2.0.0.1003. Signed-off-by: Ryan Johnson <[email protected]>
Updates `CHANGELOG.md` to include enhancements from vmware#107. 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.
LGTM! 🚀
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
Type of Pull Request
Please describe:
Related to Existing Issues
Closes #101
Test and Documentation Coverage
Breaking Changes?