When working on other things, I found that our coverage tests were failing on master on macOS. I quickly fixed this in certbot/certbot#7972, but there's nothing stopping us from hitting this problem again in the future. I think we should avoid this because it can be a confusing/frustrating experience, especially for new Certbot developers, to investigate test failures on

Beyonce said it best. If you like it then you shoulda put a test on it. Scenarios I like:

• Cert is created with right DN
• Cert is stored to X509Store after creation
• Cert request is not resubmitted
• Handles failures gracefully
• HTTP challenge/response works as expected
• Certificate renewal when cert is about to expiration

It's not really clear how "orders" are stored or how they are related to New-PACertificate.

As someone who is unfamiliar with ACME, I read in one of these issues that New-PACertificate is pretty much the same as Renew if an order exists. It wasn't clear to me that orders apparently only exist locally.

I want to renew my certificate as necessary from a cron-scheduled GitHub Action. Howe