| In order for Impact Analysis to work with Hiera data, PDB is going to store the list of Hiera keys looked up while compiling that node's catalog. We don't want to do this collection every time, because it is more expensive and unlikely to be changing much most of the time. We need to decide on a strategy for refreshing the collected data. Some ideas include: 1) On an interval. We would need to determine the frequency. 2) Based on heuristics (e.g. if the node has no data yet, facts have changed, or the code version has changed). We would need to determine what markers to watch. 3) On a change to Hiera data. We would need to integrate with CD4PE and have it trigger a collection compile on the affected node when it deploys code. |