-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: DNS reconciler engine #441
Conversation
Part of #396 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for getting to this so quickly.
This is going to need a bunch of tests in follow-ups. cc @cychu42, @Eakam1007, @Genne23v, @sfrunza13, @SerpentBytes who can probably all lend a hand with reviews and writing tests in the future.
For sure, I know how important this is for the project and the team. Actually, if this passes reviews, we could completely drop the queue based DNS system, and tie this single call in after any I don't think that we have too much traffic on staging, so I'm not too afraid of race conditions until I'm able to finish the scheduler for this. (also, the next reconciliation run would immediately fix any issues if we actually encounter a race condition) In the meantime, this seems to work, and insert / update / delete recordSets correctly in Route53 ==> the cert generation might just work after we migrate to this (would also immediately kill all drift between our db and Route53 on staging) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is looking good. I have one question about whether using an instance vs. module functions would improve maintainability, but otherwise, I think we should get others to review this and land it so we an start testing and building the code around it.
#438 deals with the database side of using multiple values for a given record name+type. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks sane to me, but without tests I have no idea. Let's try it and build around and on it.
Thanks everyone for the reviews and suggestions. Your ideas helped a lot! |
No description provided.