letsencrypt: Add support for ClouDNS provider

[tedski]

Adds support for ClouDNS provider for Let's Encrypt SSL certificates. Uses the certbot-dns-cloudns plugin.

[home-assistant]

Hi @tedski

It seems you haven't yet signed a CLA. Please do so here.

Once you do that we will be able to review and accept this pull request.

Thanks!

[home-assistant]

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

Stale

[agners]

It seems there is a minor linter error which needs addressing.

probably also make sense to add documentation for this provider, along with the two authentication options (auth_id/sub_auth_id).

[agners]

Fixes: #1022

[tedski]

I see the pip dependency issue and will work on that today.

[tedski]

It seems there is a minor linter error which needs addressing.

probably also make sense to add documentation for this provider, along with the two authentication options (auth_id/sub_auth_id).

Oops! I missed the Example configs section. Will update that.

[tedski]

Waiting on dep bump in inventage/certbot-dns-cloudns#4

[home-assistant]

Hello @tedski,

When attempting to inspect the commits of your pull request for CLA signature status among all authors we encountered commit(s) which were not linked to a GitHub account, thus not allowing us to determine their status(es).

The commits that are missing a linked GitHub account are the following:

• 7b105c71d5d7b541493d9883236d0876bfafb465 - This commit has something that looks like an email address (tstrzalk@tstrzalk-mn3.linkedin.biz). Maybe try linking that to GitHub?.

Unfortunately, we are unable to accept this pull request until this situation is corrected.

Here are your options:

1. If you had an email address set for the commit that simply wasn't linked to your GitHub account you can link that email now and it will retroactively apply to your commits. The simplest way to do this is to click the link to one of the above commits and look for a blue question mark in a blue circle in the top left. Hovering over that bubble will show you what email address you used. Clicking on that button will take you to your email address settings on GitHub. Just add the email address on that page and you're all set. GitHub has more information about this option in their help center.

2. If you didn't use an email address at all, it was an invalid email, or it's one you can't link to your GitHub, you will need to change the authorship information of the commit and your global Git settings so this doesn't happen again going forward. GitHub provides some great instructions on how to change your authorship information in their help center.

   • If you only made a single commit you should be able to run

     git commit --amend --author="Author Name <email@address.com>"
     

     (substituting "Author Name" and "email@address.com" for your actual information) to set the authorship information.
   • If you made more than one commit and the commit with the missing authorship information is not the most recent one you have two options:
     1. You can re-create all commits missing authorship information. This is going to be the easiest solution for developers that aren't extremely confident in their Git and command line skills.
     2. You can use this script that GitHub provides to rewrite history. Please note: this should be used only if you are very confident in your abilities and understand its impacts.
   • Whichever method you choose, I will come by to re-check the pull request once you push the fixes to this branch.

We apologize for this inconvenience, especially since it usually bites new contributors to Home Assistant. We hope you understand the need for us to protect ourselves and the great community we all have built legally. The best thing to come out of this is that you only need to fix this once and it benefits the entire Home Assistant and GitHub community.

Thanks, I look forward to checking this PR again soon! ❤️

Stale

[tedski]

Waiting on dep bump in inventage/certbot-dns-cloudns#4

Dependency was updated to support newer acme versions. We should be good to go now.

[tedski]

I seem to have added the bot as a reviewer accidentally. I'm not sure if this will block the merge process from any automation, but I don't seem to be able to remove the bot from the reviewers list. Let me know if there's anything else I need to complete to get this merged.

[agners]

All good, sorry I missed merging this.