FYI the "excludeCollections" actually doesn't work. for directus-sync, collections are "roles", "flows", "policies"... etc and not the actual table names. DB_EXCLUDE_TABLES is what we need and sufficient for the purpose.
I found an extremely weird bug. When using the Directus API to update fields that have onCreate/onUpdate hooks(or special attributes like date-created/date-updated) applied to them, Directus silently ignores the values you pass in your JSON payload. Instead, Directus will use its own internal logic to set these field values, regardless of what you explicitly provide in your API request.I found it by writing unit tests. I'm starting to like writing specifications / tests more.My new development loop looks like this: