charlotteguard
commented
2 months ago From steve: Rough idea of how we might do this ... write a node script that imports our hooks to fetch all centers' metadata, maps, forecasts, warnings, observations, etc - basically our startup preload bit. That runs the schema validators on it. Use a scheduled GitHub action to run it daily.
stevekuznetsov
It would be really helpful to know if thing change on the NAC side. One way is certanly Chris letting us know via email or slack or some other mechanism but that may have a delay. A few other ideas how we can possibly find out about changes: Create a GitHub action that makes calls to the most common NAC APIs we use that would compare what it receives back to what we expect (i.e. fields names we expect, if values have locked in options do they match the list we have, etc) If any changes occur, alert a slack channel or send notification via email (or both?) Create a GitHub action (possibly on the NAC side) that sends us a message if certain files in their github repo were edited recently, maybe summarizing the changes in some way. This will allow us to make time to take a look if the changes may impact us (this is likely something that wont be as useful as option 1 since we wouldn't know if changes created issues or not, but it may be helpful for more foundational changes that we may not catch right away via simple api calls) but then again how often would the NAC make changes like that?
Suggestion would be prioritize option1, and then decide if something like OPtion 2 would even be useful long term.
API calls we should cover: avalanche forecast for NWAC zones (checking that zone ids match) observation api to get observation api to post (into staging? or as private ob? delete immediately after submission) weather data for NAC weather station data NAC center metadata