انتقل إلى المحتوى
#0858
CronContainers

Every crontab in the company, read without a shell

"What runs at night?" has no answer that doesn't involve SSH into nine servers and someone's memory of a machine that was decommissioned in March.

Every container's cron kit answers it at a URL. GET .../cron-1.../users/root/crontab returns the raw table as one text blob; /users/{user}/entries returns the same thing as structured entries with ids. A loop over your container list, one GET each, writes the whole company's schedule into a file by container and user, every Monday, with a diff against last Monday. New nightly job? It's in the diff. Job that quietly disappeared? Also in the diff. Nobody granted anyone shell access; the proxy token is the credential, and it reads, it doesn't edit.

The night schedule is a diff you read at 9am.