duckdns: strip whitespace from API token - #4814
Conversation
Copy-paste from duckdns.org often includes a leading space. Strip whitespace after reading the token so IP updates do not fail with KO / empty WARNING.
Trim whitespace from the SYS_TOKEN variable.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 8 included reviews per hour; 7 remain after this review. 📝 WalkthroughWalkthroughThe DuckDNS service and root hook now remove whitespace from configured token values before DuckDNS updates and certificate-renewal operations. ChangesDuckDNS token normalization
Estimated code review effort: 1 (Trivial) | ~5 minutes Merge Risk: ⚪ Minimal · up to The add-on now normalizes configured DuckDNS tokens in both update paths, preventing whitespace-related API failures. No current merge-blocking risk remains. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Full details: Docstring CoverageExplanation No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 1 files. (1 skipped: 1 unsupported.) ✨ 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 |
Helped a friend debug empty
WARNING:lines every 5 minutes. DuckDNS was returningKObecause the token had a leading space from copy-paste on duckdns.org.Same class of bug as #2864.
This strips whitespace after reading the token in the IP update loop and the Let's Encrypt hook. Left version/changelog for you to bump on merge.
Summary by CodeRabbit