Rudder plugins » Datasources

The hard thing is to trigger a policy generation at the best time.

Too soon (after first node update) a generation will be triggerd with invalid / not up to date data for all Nodes) and a second generation will be needed
and risk to accumulate generation (should be treated correctly but we never now)

Too late, risk to miss some node updated

Best place would be as a posthook of datasource update ... but don't know if that is possible right away

To be more precise, we can't always trigger a generation, else we will loop in the case where "trigger datasource on generation" is checked. So we need to be smarter and only trigger on change.