[DevOps]: Validate diagnostics linking on Chrysalis and Spin #369

Task Details

Follow up to #367

We need to test if the cron job scanner is actually functional.

Steps to Complete

1. Follow these instructions to test dry-run and apply for diagnostics linking on Chrysalis (specify env=dev)
   • https://simboard.readthedocs.io/en/latest/operations/setup-ingestion-operations/#diagnostics-linking
2. Review latest crontab.example with diagnostic entries

   • simboard/backend/app/scripts/ingestion/sites/templates/crontab.example

     Lines 67 to 78 in d2a4f7f

     	# =============================================================================
     	# Diagnostics scans
     	# =============================================================================
     	# Link diagnostics daily at 14:00 UTC with independent locks and API credentials.
     	# DRY_RUN=false enables linking regardless of ingestion's global run mode.
     	# Use true for an optional offline scan. Archive settings are in
     	# diagnostics_archives.py; ingestion year/case limits do not apply.
     	# Development
     	0 14 * * * DRY_RUN=false SIMBOARD_ENV_FILE="${SIMBOARD_ROOT}/operations/env.dev.sh" "${SIMBOARD_ROOT}/repository/simboard/backend/app/scripts/ingestion/sites/site_ingestion_launcher.sh" chrysalis diagnostics
     	# Production
     	0 14 * * * DRY_RUN=false SIMBOARD_ENV_FILE="${SIMBOARD_ROOT}/operations/env.prod.sh" "${SIMBOARD_ROOT}/repository/simboard/backend/app/scripts/ingestion/sites/site_ingestion_launcher.sh" chrysalis diagnostics

3. Update current crontab to include those diagnostic lines
4. Validate that the crontab diagnostic entries are working with cron

Additional Notes

Note: I need to fix DRY_RUN=false being specified directly on the lines. I think it should inherit the DRY_RUN configuration already specified here