notify/pushover: trim whitespace from token and user key files - #5398
notify/pushover: trim whitespace from token and user key files#5398dpacgdm wants to merge 1 commit into
Conversation
Editors often append a trailing newline; Pushover rejects those values as invalid credentials. Match other notifiers that already TrimSpace file-backed secrets.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughPushover now trims whitespace from credentials read through ChangesPushover credential handling
Estimated code review effort: 1 (Trivial) | ~5 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Confirming from production on 0.33.1, with one detail I don't see recorded here Three-site Prometheus/Alertmanager fleet, zero pages delivered for six days — The trigger is moving credentials from inline Small clarification on the API: Pushover accepts a trailing space and Also worth noting for review: #3641 has been open since December 2023 and this is 8 lines with tests — would |
|
I think it makes sense to add a separate new test instead of modifing the existing one because files without an extra newline are not properly covered anymore. Also Commit signature is missing. Please use the existing PR template |
Summary
token_fileanduser_key_file(same pattern as pagerduty/slack/etc.).Related to #3641
Test plan
go test ./notify/pushover/ -count=1\nand still succeed