Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upOctodns-sync support sync without override the dynamic records #424
Comments
|
The easiest way I found is to
|
|
@brianeclow Thank you. |
This isn't possible with octoDNS as it's designed to work without any extra metadata so it wouldn't be able to know which records it owns (and needs to manage including deletes) and which records it would need to leave alone. The recommendation from @brianeclow is the best option I can think of us as well. If you dump the full zone and then go through and exclude the things you don't want it to touch seems like it'll get the desired behavior. |
We have a usercase where dynamic records get create/delete through TF or ruby/python r53 api's when we provision and tear down the resources. In the same zone, we have some static records requests that come through from support where we are trying to streamline using octodns and git for version control.
One way to achieve would be to take octodns-dump and make necessary changes push to git and sync. Still, we may see some dynamic records that may get-in in the meantime. So one thought would be something like
octodns-sync --config-file=./config/production.yaml --no-deleteA flag that can override only the records that it finds in its .yaml and ignore the rest of the records.
any thoughts, please share.