-
Notifications
You must be signed in to change notification settings - Fork 1
Use icinga-go-library
#114
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
Conversation
0223bed to
387ce31
Compare
4a65442 to
4153415
Compare
4153415 to
fa519f9
Compare
20f1849 to
88e5158
Compare
88e5158 to
996fd95
Compare
6287c2e to
4ae3893
Compare
|
I had to use the new, not yet merged PR as the icinga-notifications/internal/event/event.go Lines 136 to 137 in 4ae3893
|
0e466c9 to
b68f4f6
Compare
cf958eb to
bba22c5
Compare
oxzi
left a comment
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.
Please feel free removing the now unused utils functions. Otherwise, LGTM.
go.mod
Outdated
| github.com/goccy/go-yaml v1.11.3 | ||
| github.com/google/uuid v1.6.0 | ||
| github.com/icinga/icingadb v1.1.1-0.20230418113126-7c4b947aad3a | ||
| github.com/icinga/icinga-go-library v0.1.1-0.20240529153148-5054d55f8005 |
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.
I just tagged the new version as v0.2.0, please update this to use the tagged version.
The `context.Context` related changes are neccessary as otherwise you will have to wait for 5m when having Icinga notification started with invalid database config due to the internal database.Connect retrials. Lastly, the logging related changes are useful as we want to properly render the stack traces when we unexpectedly exit from the main function instead of wrapping the error in a confusing `zap.Error()` json key.
Blocked By
DB#BuildColumns()icinga-go-library#22