Impact evaluation question about this: who is currently using the /search/ endpoint?
Can we change it without breaking anything, or should the change be coordinated with other components?

Impact evaluation question about this: who is currently using the /search/ endpoint?

From the top of my head:

• www.s.o
• You (or olasd) also mentioned a gist of at least one person using it as well.

https://gist.github.com/search?utf8=%E2%9C%93&q=archive.softwareheritage.org

Can we change it without breaking anything, or should the change be coordinated with other components?

When deploying to moma, we'll need to deploy the url fix to www.s.o as well.

And also, our main puppet default.yaml where the open endpoint would also change from the old one to the new one.

And last, the front-end of the webapp (/browse).

JFTR, other endpoint names that were considered but dropped:

• /content/search/: we're not doing a generic search, and it will also be the first API endpoint with a verb
• /content/existence/ or /content/presence/: they can get confusing with content_status=absent

We also need to update the icinga check for that particular endpoint.
This is done.

I notified where it was used:

• https://gist.github.com/atomotic/c271159eabc7ec4516c23cbde9b37f48#gistcomment-1974409
• https://gist.github.com/atomotic/87bb08209cbeea3778063118aa945a26#gistcomment-1974417