Deploy webhook using ansible #36
Conversation
|
@snacktavish NB - Regarding the amendments webhook, the old (pre-Pyramid) handler is on branch I'll comment this out in the Ansible playbook, but keep the main (study) webhook. I believe this is pointing to the correct (new) URL. |
|
@snacktavish I spoke too soon! It looks like the amendments webhook handler doesn't just clear stale amendments from the cache -- it also does some processing via EDIT: I found this old method in taxomachine. I'm guessing there's a newer implementation that we should call instead..? Or we need to write one. |
This reverts commit c2bb878.
|
Yep - we need to put it into otindex. And I pulled the code that was in phylesystem API here: But haven't had a chance to look at the taxon updates yet. Feel free to take a crack at it if you want! |
This mirrors our explicit rewriting of /cached/ calls.
We'll install the amendments webhook once we have a working handler and URL for processing newly-saved amendments.
|
NB - Managing Github webhooks requires the Ansible user to have a valid personal access token on their local filesystem, at |
|
These changes are working now on devtree/devapi. Ready to merge? |
This is here just as a reminder that we should redirect *both* cache-related URLs if this config template is used.
This should install an appropriate webhook to update otindex when a study is saved in the curation app.