Octodns-sync support sync without override the dynamic records

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-delete

A flag that can override only the records that it finds in its <zone>.yaml and ignore the rest of the records. any thoughts, please share.

[viranch]

Side note: --no-delete can be achieved by setting delete_pcent_threshold to 0. See https://github.com/octodns/octodns/blob/07aad17/docs/records.md#restrict-record-manipulations

[ross]

This is now also possible with the use of processors, though there’s no in-built processor that would specifically ignore dynamic records. It would be possible to build such a thing. It may be easier to stick with the exclude stuff recommended above. Either way I believe there are options to solve the use case so closing. Feel free to reopen if not.