Testing out the beta Cloudflare SDK

[jacobbednarz]

👋 thanks for keeping this project going! it's been a great source of improvements for the cloudflare-go library and as a by product, the Terraform Provider.

we've been working on a beta of the cloudflare-go library (cloudflare/cloudflare-go#1538) that is generated from our OpenAPI schemas and if you've got some free time, i'd love you to kick the tyres on it and let us know if you have any feedback! (no pressure of course). we have a migration guide included but you're also welcome to just eyeball it and see if it all feels like it should.

if you do find anything that doesn't work nicely for your use case, or just have some design/library wide questions, please don't hesitate to drop them into the linked discussion.

cheers!

[favonia]

@jacobbednarz I will have time working on this after finishing up #797. Sorry about the loooooong delay!

[jacobbednarz]

all good, no rush at all!

[favonia]

@jacobbednarz I'm just writing down my own notes for my self. There's no new information.

Observed Improvements of the New SDK

• It offers significantly better error handling: a reliable way to tell whether an error is from the Cloudflare API or other networking issues.
• It resolves a long-standing issue where zero values in Go might be unintentionally omitted when generating JSON requests. This was addressed on a case-by-case basis in the old SDK, and the new SDK adopts a systematic solution, albeit adding some overhead.
• The code is (almost?) perfectly synchronized with the new API documentation site.
• The immediate availability of the DNS batch API. Use the new batch API for DNS records #963

Blocker

The only blocker seems to be the lack of the ability to easily create a "clean" client from the new API. This can be worked around by undoing the reading of environment variables. The above improvements might eventually convince me to adopt the new SDK with such a workaround.

[jacobbednarz]

thanks for kicking the tyres here and keeping us updated ❤️

The code is (almost?) perfectly synchronized with the new API documentation site.

there is currently a one hour (maximum) delay. they are built and triggered from the same pipeline.