INWX: Fix INWX provider after their unexpected data-type breaking-change#3855
Merged
tlimoncelli merged 3 commits intoStackExchange:mainfrom Nov 29, 2025
Merged
INWX: Fix INWX provider after their unexpected data-type breaking-change#3855tlimoncelli merged 3 commits intoStackExchange:mainfrom
tlimoncelli merged 3 commits intoStackExchange:mainfrom
Conversation
Collaborator
Author
|
Couldn't run the entire test unfortunately, as the sandbox is sporadically offline/running into timeouts... |
Collaborator
Author
|
@tlimoncelli It's ready to be merged to fix INWX. |
tlimoncelli
approved these changes
Nov 29, 2025
Contributor
|
yay! thanks for fixing this! it was a great group effort! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #3854
Unfortunately I couldn't run the integrationTests properly as INWX doesn't seem to have properly updated their sandbox environment (it still presents
intinstead ofstringlike production). Hence, the tests do fail. I don't want to run this against my own production account, to be frank.See:
Hence, only done manualy tests via
dnscontrol push --domains <example.com>:(tested create, delete and modify)