What mechanism keeps pushing the bigip.conf and bigip_base.conf files to the load balancers?

I have been cleaning out orphaned rows from the neutron LBaaS tables. I want to match the F5 configuration to what is ACTIVE in the vips, pules, poolmonitors, etc neutron tables.

The quickest way I would like to do that is to delete the bigip.conf and bigp_base.conf files from each unneeded partition then run a tmsh load sys config partition { partition }, but something is putting those files back in the /config/partitions/ directories.

I don't know enough about the plugin to know what is doing that. My assumption was the agent pulled that from the DB but conf files have pools configured when none exist in the pools table.

So if I delete *.conf files from LBaaS partitions, how are they getting back on the F5? Is it the LBaaS plugin, or neutron or something on the F5?

These are Viprion B2150 blades on 11.5.1 HF2