Jeff Geerling

Shouldn't have been closed. I'm open to a PR that only does these things (and doesn't affect SSL configs, as #131 did).

Every time I come back to this PR, I spend a lot of time thinking whether I should consider merging it or not, commenting on it or not, etc. I...

I wonder... since there are other CLI options too, which people may want control over... maybe we should just have a var like `certbot_create_extra_args` and you can throw whatever you...

Yeah, definitely! I'll take a look at the PR (noting that I'd rather not merge until we can find a way to make it pass tests).

Just giving a second pass here—I still do like the idea, but one thing that may help in many cases is to [have test/non-public environments generate a self-signed cert instead](https://www.jeffgeerling.com/blog/2017/generating-self-signed-openssl-certs-ansible-24s-crypto-modules)....

I do think we should allow the use of the staging environment (e.g. for CI, local testing, etc.), so will add a label to prevent stale bot from taking down...

I'm on the fence on this; I don't generally like to pollute managed directories with files to track state, and that's what this seems to be doing (maintaining a list...

I do want to fix this. I'm just giving it more time for consideration. I just hate adding state and complexity that this role introduces and then relies on.

At this point (about a year later), it seems like the Docker repos support ARM more easily, and it might be okay to put the arm-based role back into this...

Heh... "planned" just means (for me, at least) I 'plan' on doing something with the issue, and I don't want it to auto-close :)