YAML expiration causes fact cache to overwritten #32
Description
When using this in full auto mode, it seems that the coping the yaml cache in place the first time must basically be done prior to ever diff. As when puppet finds the yaml cache, its default expiry is the runinterveral as thus normally like 30 mins. I got around this by hacking the terminus code to disable checking expiry , along with bypassing puppetdb via routes.yaml, but we might need to ship our own termnius in this tool or alternatively submit somthing to upstream puppet to allow you to ignore expiry of the yaml cache.
This code has been in puppet for a while but seems it perhaps only started working correctly in puppetserver