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

Bump Go version to 1.16.15, prepare 3.2.2 release #199

Merged
merged 1 commit into from Mar 21, 2022
Merged

Conversation

bflad
Copy link
Member

@bflad bflad commented Mar 21, 2022

Reference: golang/go#51127
Closes #157
Reference: #188 (I'd like to verify this is fixed after release, rather than close immediately)

Updates the testing and release processes to the latest 1.16.x version, which resolves a longstanding Go resolver issue with responses greater than 512 bytes. Verifies by enabling a previously skipped acceptance test.

Also adds CHANGELOG entries for upstream module updates which are bundled with this provider release, which may fix specific EDNS handling issues.

Reference: golang/go#51127
Reference: #157
Reference: #188

Updates the testing and release processes to the latest 1.16.x version, which resolves a longstanding Go resolver issue with responses greater than 512 bytes. Verifies by enabling a previously skipped acceptance test.

Also adds CHANGELOG entries for upstream module updates which are bundled with this provider release, which may fix specific EDNS handling issues.
@bflad bflad added this to the v3.2.2 milestone Mar 21, 2022
@bflad bflad requested a review from a team as a code owner March 21, 2022 12:41
Copy link
Contributor

@detro detro left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

One observation that I don't think we can't do anything about: the tests in this provider are "risky". The fact that they execute real DNS resolutions has the chance to fail if thing change or temporary outages occur.
It would be awesome if we could spawn a DNS server.
SCRAP THAT!

Curious, I dug into how the automation is wired up, and saw that we do exactly that: spawn local DNS servers to simulate various scenarios and then run the tests against it.

Kudos and, once more, LGTM! 👩‍🍳 💋

@bflad
Copy link
Member Author

bflad commented Mar 21, 2022

Yeah, ideally, we'd implement our own DNS server in Go for the "regular" DNS query testing if/when those data sources allow lookup via custom resolver, but the effort/benefit ratio hasn't made it worth it in the past.

@bflad bflad merged commit 9e4728f into main Mar 21, 2022
@bflad bflad deleted the bflad-v3.2.2 branch March 21, 2022 13:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

data-source/dns_txt_record_set: Large (>512 byte) Records Return Errors
2 participants