Check hosted zone changes INSYNC

[tamsinforbes]

👀 Purpose

• To check the change status

♻️ What's changed

• ✨Workflow to check the change status of a recently implemented change
• ✨Script to collect the list of changed hosted zone files, and from these collect the hosted zone names, IDs, poll CloudTrail for the most recent changes to these and collect the change ID then collect the latest info on that change ID
• ✨Added CloudTrail service to collect the latest n change resource record sets
• ✨Added to the Route53 provider class a method to collect the change status given a change ID.
• 🧪 Suite of tests

📝 Notes

• Set to run on workflow_run after successful completion of the OctoDNS Sync workflow - ought to collect the code delta from the merging PR to get the list of hosted zone names that have been changed (this is usually one only).
• AWS should propagate changes to their DNS authoritative resolvers within 60 secs

[github-actions]

🦙 MegaLinter status: ✅ SUCCESS

Descriptor	Linter	Files	Fixed	Errors	Elapsed time
✅ YAML	prettier	1	1	0	0.26s
✅ YAML	yamllint	1		0	0.18s

See detailed report in MegaLinter reports
Set VALIDATE_ALL_CODEBASE: true in mega-linter.yml to validate all sources, not only the diff

MegaLinter is graciously provided by

[tamsinforbes]

How quickly will changes I make to my DNS settings on Amazon Route 53 propagate globally?

Amazon Route 53 is designed to propagate updates you make to your DNS records to its world-wide network of authoritative DNS servers within 60 seconds under normal conditions. A change is successfully propagated world-wide when the API call returns an INSYNC status listing.
Note that caching DNS resolvers are outside the control of the Amazon Route 53 service and will cache your resource record sets according to their time to live (TTL). The INSYNC or PENDING status of a change refers only to the state of Route 53’s authoritative DNS servers.