-
-
Notifications
You must be signed in to change notification settings - Fork 2
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
feat: Support root nameserver and additional record types #40
Conversation
Ideally the caveats would be catched/fixed in the planning/validating phase but couldn't find any documentation or examples how to. |
You can search the org for what various providers are doing/checking in that function: https://github.com/search?q=org%3Aoctodns%20_process_desired_zone&type=code The azure provider looks like it has something that's fairly close to the root caveats: As for the TTL bit I'm not sure what makes sense. It could always warn if there's a non-matching value and just go ahead with that value or it could do the standard |
|
Changed it to draft for now, The opt-in for NS is a pain in .... when dealing with larger sets of domains in the config. Trying to refactor to something like the googlecloud provider:
|
IIRC that's just using the default/built-in root handling of the base class. |
Basic functionality of octodns allready takes care of non-existing root-ns records in source. Also gave all api-calls a dedicated try block so more specific exceptions can be raised (and tested)
@ross Thanks for the info. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall looks good. Few minor things inline and it should be ready to 🚢
Thanks.
Co-authored-by: Ross McFarland <rwmcfa1@gmail.com>
This reverts commit 62f93de.
…tion from code review.
Thought i tried that before without success, but maybe did something else wrong then. Removed the usage of .data for both the |
Thanks. |
@ross Do you have an idea when the next release of the provider will be (and/or when it will be included within the docker containers, github action etc etc) |
/cc #42 |
This PR will add support for all additional record types transip supports at the moment: