-
Notifications
You must be signed in to change notification settings - Fork 0
Description
Could we create scripts that are enterprise that do not belong to any one district? Currently I believe we target a district and it pulls scripts from their repo.
But possibly an "enterprise" option that pulls scripts for adhoc run there.
Then also potentially have a scheduler in airflow for these enterprise jobs to run as well. We have wm-swt-cwbi-jobs but perhaps a wm-wmes-cwbi-jobs as well?
I'm thinking once a night we:
- Target
*.PDFthat have been added for a given district to the blobs endpoint that have not been previously scanned - Trigger a 508 scan against each pdf
- Email the results and/or create a report of results and store the report to the internal S3 website
There's some details to be worked out here. Such as responsibility, but we have the opportunity to give a best effort forward for 508 scanning for districts using enterprise infra.
Alternative
We add a script to existing Airflow as a standalone that does the 508 scan from Blob. But having it in the WMES/adhoc jobs infra ensures it remains closer to district responsibility. It also would allow for tweaks in what would be running the 508 scan (image).