Batching DNS changes about sewer HOT 3 CLOSED

Hi,

First; thanks for using sewer and I'm glad to hear it seems to work for you. It's interesting that you are using it in AWS lambda no less.

What you are asking for sounds easy to do - off the top of my head- .
We would just need to move this line from inside the loop;

However, I cant think of a way -again off the top of my head- to implement it in a backward compatible manner. This is because the method, create_dns_record;

I'll mull on this for sometime. I'm happy to hear suggestions.

from sewer.

or maybe if we used asyncio, we could race requests; i dont know

from sewer.

Batching of challenges first landed in #178 in the new ProviderBase class in auth.py. A still not quite final version is in release 0.8.2, and further refinement in the work that's been seeping into master since the release.

Of course the batching can't do anything immediately for the legacy DNS classes, but there's now an interface to migrate them to that can take advantage of batching. I think that addresses as much of this bug as I can - services that don't admit that there may be multiple occurrences of a record type for a single identity are... Well, we can always hope it's just their API that comes up so short, and that they fix it.

from sewer.