Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Certbot library usage #4065
Would it be possible to refactor
Referencing #1793, #358, #1299 as semi-related items, although they are more focused on refactoring the
I think this would lead to greater uptake from hosting providers (easier implementation), as it becomes much simpler to integrate into a fully automated certificate generation process.
I created a wrapper around
Thanks - I have seen
As I also mention, it's nice to maintain compatibility with
A fair bit of boilerplate is needed and as things change moving forward, an implementation using
Just putting the thought out there - if it isn't desirable, then by all means, close this issue.
No this is definitely desirable and actually something we've talked about internally. Certbot/acme is rarely used by hosting providers who support Let's Encrypt and we believe the problems you describe in this issue are largely the reason. These companies need a library and
To be honest, I doubt we'll see this change for a while, but we'll certainly keep it in mind. We're currently working on getting things polished up and increasing stability so we can get Certbot 1.0 out the door. We do, however, have big plans for Certbot 2.0 as we've learned a lot while writing and deploying Certbot to a large user base with a changing protocol. I think this is something important for us to keep in mind then.
Adding my +1 here. Over the weekend I refactored the Boulder integration test to use the
It was harder than I expected. Main pain points: