certbot
--certbotv1.2.0Converts `certbot` command output to JSON
LinuxmacOSFreeBSDcommand
$ certbot | jc-rs --certbotA real pair
From the reference corpus (generic/certbot-account.json). The left pane is the input the fixture ships; the right pane is the corpus's expected JSON. CI compares jc-rs with it field by field under the published differential. Hover a value to see where it came from.
certbotgeneric
Saving debug log to /var/log/letsencrypt/letsencrypt.log Account details for server https://acme-staging-v02.api.letsencrypt.org/directory: Account URL: https://acme-staging-v02.api.letsencrypt.org/acme/acct/12345679 Email contact: some@example.com
expected outputjson
Use the Left and Right arrow keys to highlight the matching value in the input.
{ "account": { "server": "https://acme-staging-v02.api.letsencrypt.org/directory", "url": "https://acme-staging-v02.api.letsencrypt.org/acme/acct/12345679", "email": "some@example.com" } }
Fixture coverage
3/3oracle-valid pairs match under the published structural JSON comparison
Magic syntax
jc-rs certbotjc-rs runs the command itself and parses what it prints. Recognised for: `certbot`Source: crates/jc-rs-parsers/src/security/certbot.rs. jc-rs targets the schemas defined by the original Python tool. Fixture coverage above is the measured evidence for this parser; test the inputs your pipeline depends on. Compare