go-ethereum

Commit Graph

Author	SHA1	Message	Date
Felix Lange	d3c1e654f0	cmd/devp2p: be very correct about route53 change splitting (#20820 ) Turns out the way RDATA limits work is documented after all, I just didn't search right. The trick to make it work is to count UPSERTs twice. This also adds an additional check to ensure TTL changes are applied on existing records.	2020-03-26 23:55:33 +01:00
Felix Lange	976a0f5558	cmd/devp2p: fix Route53 TXT record splitting (#20626 ) For longer records and subtree entries, the deployer created two separate TXT records. This doesn't work as intended because the client will receive the two records in arbitrary order. The fix is to encode longer values as "string1""string2" instead of "string1", "string2". This encoding creates a single record on AWS Route53.	2020-02-05 15:29:59 +01:00
Felix Lange	0af96d2556	cmd/devp2p: submit Route53 changes in batches (#20524 ) This change works around the 32k RDATA character limit per change request and fixes several issues in the deployer which prevented it from working for our production trees.	2020-01-17 11:32:29 +01:00

Author

SHA1

Message

Date

Felix Lange

d3c1e654f0

cmd/devp2p: be very correct about route53 change splitting (#20820 )

Turns out the way RDATA limits work is documented after all,
I just didn't search right. The trick to make it work is to
count UPSERTs twice.

This also adds an additional check to ensure TTL changes are
applied on existing records.

2020-03-26 23:55:33 +01:00

Felix Lange

976a0f5558

cmd/devp2p: fix Route53 TXT record splitting (#20626 )

For longer records and subtree entries, the deployer created two
separate TXT records. This doesn't work as intended because the client
will receive the two records in arbitrary order. The fix is to encode
longer values as "string1""string2" instead of "string1", "string2".
This encoding creates a single record on AWS Route53.

2020-02-05 15:29:59 +01:00

Felix Lange

0af96d2556

cmd/devp2p: submit Route53 changes in batches (#20524 )

This change works around the 32k RDATA character limit per change
request and fixes several issues in the deployer which prevented it from
working for our production trees.

2020-01-17 11:32:29 +01:00

3 Commits