-
Notifications
You must be signed in to change notification settings - Fork 101
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
updown monitor support in Ingress Monitor Controller #152
Conversation
Softagram Impact Report for pull/152 (head commit: 5e09602)⭐ Change Overview
📄 Full report
Give feedback of this report to support@softagram.com |
@aliartiza75 Yikes! You better fix it before anyone else finds out! Build 1 has Failed! |
…d of updown monitor, added httpStatusCodesMap file that contains a map of status codes, delete test file for now and fixed typo in pingdom monior
updownService.apiKey = confProvider.ApiKey | ||
updownService.alertContacts = confProvider.AlertContacts | ||
// creating updown go client | ||
httpDefaultClient := http.DefaultClient |
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.
ineffectual assignment to httpDefaultClient
(from ineffassign
)
@aliartiza75 Yikes! You better fix it before anyone else finds out! Build 2 has Failed! |
@aliartiza75 Yikes! You better fix it before anyone else finds out! Build 3 has Failed! |
// UpdownMonitorService struct contains parameters required by updown go client | ||
type UpdownMonitorService struct { | ||
apiKey string | ||
url string |
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.
url
is unused (from structcheck
)
@aliartiza75 Image is available for testing. |
@aliartiza75 Yikes! You better fix it before anyone else finds out! Build 5 has Failed! |
@aliartiza75 Yikes! You better fix it before anyone else finds out! Build 6 has Failed! |
@aliartiza75 Yikes! You better fix it before anyone else finds out! Build 7 has Failed! |
@aliartiza75 Image is available for testing. |
@aliartiza75 Image is available for testing. |
@aliartiza75 Yikes! You better fix it before anyone else finds out! Build 10 has Failed! |
@aliartiza75 Yikes! You better fix it before anyone else finds out! Build 11 has Failed! |
@aliartiza75 Yikes! You better fix it before anyone else finds out! Build 12 has Failed! |
@aliartiza75 Yikes! You better fix it before anyone else finds out! Build 13 has Failed! |
@aliartiza75 Yikes! You better fix it before anyone else finds out! Build 14 has Failed! |
@aliartiza75 Yikes! You better fix it before anyone else finds out! Build 15 has Failed! |
@aliartiza75 Yikes! You better fix it before anyone else finds out! Build 16 has Failed! |
@aliartiza75 Yikes! You better fix it before anyone else finds out! Build 17 has Failed! |
…est.go file updated by updating configs pull calls
@aliartiza75 Yikes! You better fix it before anyone else finds out! Build 18 has Failed! |
…e-status-page_test.go file
@aliartiza75 Image is available for testing. |
@aliartiza75 Image is available for testing. |
…n-monitor.go file
@aliartiza75 Image is available for testing. |
this PR resolves this issue #93