CI: check server metadata on a schedule #516
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #515
Todo
dev
,test
, andprod
ACTION_MONITORING_SLACK
secretACTION_MONITORING_SLACK
METADATA_CHECK_CONFIG
secretMETADATA_CHECK_CONFIG
:Reviewing
Success path
Checkout the branch locally, open in devcontainer
Create a file
metadata.json
at the root, with contents:Run
flask init-db
to ensure metadata is hydratedF5
to run the appRun the
check-metadata
script:python .github/workflows/check-metadata.py cst
Confirm no error output. Zero exit code.
Fail path
eligibility_server/db/setup.py
to makemetadata.timestamp
something other than the correct current date (e.g. change day, month, and/or year)flask init-db
again to hydrate new metadataF5
to run the appcheck-metadata
script:python .github/workflows/check-metadata.py cst
Redo the preceding steps to:
metadata.users
0metadata.eligibility
an empty listAnd in each case, confirm the
check-metadata.py
script fails accordingly.