ACK’d. I’ll open an update pull-request today.
It hasn’t. We haven’t talked about it much within the team but I’m somewhat against the idea of automating the update of the library itself. It may be better to change the implementation to support live-reloading of new PSL contents on a fixed interval. We use
godep right now to manage vendored dependencies and it can be extremely fickle even when used manually.
This is mostly one of those places where the pain of the awkward manual approach is infrequent enough that we haven’t been able to divert resources to fixing it compared to other things
When we initially switched from using the copy of the PSL in the Go standard lib to Weppos’
publicsuffix-go library one of the appeals (If I remember correctly) was that the library also supported transitioning to having a process where the raw PSL list can be updated alongside Boulder as a file on disk and live-reloaded by
publicsuffix-go/Boulder. We haven’t made any progress towards implementing that and presently use the copy baked into the library. I feel like this path would be a better long-term solution.