We want to keep the CUSP ARDAC data item in sync with the latest data release from the CUSP repo on Github.
For example, when CUSP gets a release 1.2 for example, we want to be able to pick that new data up as rapidly as possible.
This doesn't even need to be a regularly scheduled flow...though it could fire once a month or whatever and do a version comp
Step 1: check Github release version
Step 2: check the version of the data that exists on GeoServer
if github_version == gs_version
-- do nothing
if github verison > gs_ version:
-- download latest CUSP release CSV
-- Download letest CUSP bib
-- execute GS preprocessing script (can this be prefect native?)
-- swap in new file on GeoServer
-- run integration test (ARDAC map item)
-- run integration test (uncached API)
Flow should automatically send email ping for success / failure
Questions:
should the preprocessing script be native to the prefect repo? I think so....
We want to keep the CUSP ARDAC data item in sync with the latest data release from the CUSP repo on Github.
For example, when CUSP gets a release 1.2 for example, we want to be able to pick that new data up as rapidly as possible.
This doesn't even need to be a regularly scheduled flow...though it could fire once a month or whatever and do a version comp
Step 1: check Github release version
Step 2: check the version of the data that exists on GeoServer
if github_version == gs_version
-- do nothing
if github verison > gs_ version:
-- download latest CUSP release CSV
-- Download letest CUSP bib
-- execute GS preprocessing script (can this be prefect native?)
-- swap in new file on GeoServer
-- run integration test (ARDAC map item)
-- run integration test (uncached API)
Flow should automatically send email ping for success / failure
Questions:
should the preprocessing script be native to the prefect repo? I think so....