search

cedadev / search-futures

Future Search Architecture
BSD 2-Clause "Simplified" License
0 stars 0 forks source link

Design workflow for re-indexing when collection description document has changed #136

Open agstephens opened 2 years ago

agstephens commented 2 years ago

See Richard's PR: https://breezy.badc.rl.ac.uk/stac/stac-item-descriptions/-/commit/7b632771c23cd81ff6c8b2c4178a1bc4d75d7306

Can we review the item description repo and make it public on github?

rhysrevans3 commented 2 years ago

https://github.com/cedadev/item-descriptions

agstephens commented 2 years ago

At present we have github and gitlab repos for the collection descriptions. There are 2 important hooks:

  1. Validation: validate the contents against some rules.
    • Use PR mechanism to kick off github actions
    • PR accepted: assume valid content
  2. Trigger re-indexing of collections/items/assets:
    • K8 pods need to know when to do this
    • The controller node could routinely check for changes in the github repo and then re-scan accordingly
agstephens commented 2 years ago

See: #110