Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for Timeweb provider #1850

Merged
merged 3 commits into from
May 14, 2024
Merged

Add support for Timeweb provider #1850

merged 3 commits into from
May 14, 2024

Conversation

ostankin
Copy link
Contributor

@ostankin ostankin commented Jan 3, 2024

I'm using Lexicon as a part of Letsencrypt certbot, and I needed support for my hosting provider, Timeweb. Thanks for the contributing guidelines, they are pretty straightforward -- hopefully all the requirements have been met.

Had to skip a couple of tests since Timeweb's DNS functionality is quite crippled (more info in commit description). All other tests seem to pass.

W239 seems to be a false positive here, since it relates to a formatted
multiline description.
The implementation has been done according to the [guidelines][1], all
tests seem to be working, except for three cases:
- A type subdomain record creation (no direct support from the provider)
- CNAME type subdomain record creation (same reason)
- TTL modification (the provider uses TTL=600 for all records)

[1]: https://dns-lexicon.readthedocs.io/en/latest/developer_guide.html
From the previous steps one could imply that you are already in
`lexicon` directory, so no need to have it in the path.
@adferrand
Copy link
Collaborator

This LGTM to me. Thanks a lot !

@adferrand adferrand merged commit 0bef091 into AnalogJ:master May 14, 2024
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants