How are people testing cron job configuration in non-production environments? From our read of the documentation they only work in production deployments? This seems like a really big conceptual miss. We know we can test the endpoint directly but we want to get an actual deployment up that looks like prod as closely as possible, which includes cron jobs that could interfere with each other if we aren’t careful.
At the moment we are going to end up deploying a really dumb cron jobs microservice production project that calls an endpoint in our other preview deployment project but this is incredibly hacky and not terribly secure.
Any suggestions from the community on how you have worked around the issue?
You’re right, cron jobs currently only work in production deployments. The reason is we don’t want people to create hundreds of deployments that each will incur compute cost or cause other side effects.
This is the best option for now, but I invite others in the community to chime in with their potential workarounds.
Appreciate you taking the time to write this feedback though. I’ve shared it with the team looking at cron jobs and will loop back with any developments in the future.
