Hi, Some certbot plugin options, like --apache and --nginx, handle both authentication and installation. Others, like --webroot, --standalone and --manual, only handle authentication. The user guide naturally enough shows using certbot with the second set of options.
Is it OK to use the run subcommand, rather than the certonly subcommand, with the authentication-only plugin options? i.e. Will "run" be friendly and act like certonly, and not worry about installation, if it's using a non-installing plugin? Or will it be friendly in a different way, and report the absence of installation instructions as an error?
I know I can delete a certificate lineage and create it again to test this, and I probably will, but I thought I'd ask here first.
The reason I'm asking is that I have a program that invokes certbot. The user can supply authentication/installation options for certbot, but it currently assumes that it's OK to use certbot's run subcommand. If that's not always the case, I need to either change it to determine when to use certonly instead of run, based on the supplied certbot options, or if that's not reliably doable, I need to change it to let the user specify when to use certonly instead of run. I'd prefer it if they didn't have to do that, but it might not always be avoidable. Thanks in advance for any advice.