This repository was archived by the owner on Dec 9, 2025. It is now read-only.
This repository was archived by the owner on Dec 9, 2025. It is now read-only.
Aligning "meta" with platform? #29
Description
If users of platform-app make use of state.meta to access things like the runId, there's not much we can do about it on microservice... in that sense, it is possible to write jobs which run on platform but not on microservice. I think that's always going to be possible, and we'll have even less control over how folks build and pass around state on their own implementations.
However, I think that including a last_success timestamp is arguably valuable enough to be shared between platform and microservice... it's very useful for keeping a "cursor" between runs, allowing a cron job to access only resources that have been created/updated since the last_success -ful run of the job.
Thoughts?