Giters

certbot / certbot

Certbot is EFF's tool to obtain certs from Let's Encrypt and (optionally) auto-enable HTTPS on your server. It can also act as a client for any other CA that uses the ACME protocol.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Impossible to provide 3rd party plugin configurations in cli.ini

Fluepke opened this issue · comments

commented

My operating system is (include version):

Arch Linux

I installed Certbot with (certbot-auto, OS package manager, pip, etc):

pip

I ran this command and it produced this output:

certbot certonly --domain example.com

Certbot's behavior differed from what I expected because:

cat /etc/letsencrypt/cli.ini

; redacted for privacy reasons
authenticator=certbot-dns-powerdns:dns-powerdns
certbot-dns-powerdns:dns-powerdns-credentials=/etc/certbot-dns-powerdns/pdns-credentials.ini

I would expect this to provide the --certbot-dns-powerdns:dns-powerdns-credentials flag to certbot.

But it does not apparently:

certbot: error: ambiguous option: --certbot-dns-powerdns=dns-powerdns-credentials=/etc/certbot-dns-powerdns/pdns-credentials.ini could match --certbot-dns-powerdns:dns-powerdns-propagation-seconds, --certbot-dns-powerdns:dns-powerdns-credentials

This issue is related to

commented

Thanks for the detailed issue @Fluepke.

I think this is a duplicate of #6040 which was closed in favor of #4351.

For that reason, I'm going to close this issue. We have a couple PRs for that issue though and we're planning on catching up on PRs from open source contributors in the next few weeks so hopefully this problem will be resolved soon.

commented

Hi @bmw
this is a sad story - the problem is known since more than a year, the pull request was not merged back then, and is not working with current master branch.

That means, that till now, after at least 1.5 years (since at least June 2018), there is still no way to configure third-party plugins via config files.

Why do you close this issue? It is neither resolved, not partly resolved, nor any progress since June 2018.

commented

Hello @norbusan, @bmw closed only the issue for issue management purpose, and not because the goal expressed in the issue would be out of scope. It is just that #4351 is already tracking the problem.

About solving this, it is definitely in the scope, and we hope we will have the time to fix it ASAP.

commented

THanks @adferrand , tha tis very much appreciated. I have rebased the original PR onto the current master and adjusted it so that it loads, but it didn't work at all, unfortunately.