5 Commits (70da74e73a182620a09bb0cfbff173e6d65d0518)

Author	SHA1	Message	Date
Felix Lange	bed74b38d9	cmd/devp2p: fix comparison of TXT record value (#22572) ... * cmd/devp2p: fix comparison of TXT record value The AWS API returns quoted DNS strings, so we must encode the new value before comparing it against the existing record content. * cmd/devp2p: add test * cmd/devp2p: fix typo and rename val -> newValue	4 years ago
Quest Henkart	e3a3f7cd64	cmd/devp2p: use AWS-SDK v2 (#22360) ... This updates the DNS deployer to use AWS SDK v2. Migration is relatively seamless, although there were two locations that required a slightly different approach to achieve the same results. In particular, waiting for DNS change propagation is very different with SDK v2. This change also optimizes DNS updates by publishing all changes before waiting for propagation.	4 years ago
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.	5 years ago
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.	5 years ago
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.	5 years ago