Repository navigation
v0.6.0
A participant can ask which events they have registered for, and administrators get an API reference for every endpoint the Indico has.
Run indico db --plugin stsa upgrade after installing, then restart Indico (and the Celery worker, if you run one). This release adds a column. Until it has been run the plugin reads as nothing configured, the STSA pages in the management area say so, the new endpoint answers with an empty list, and the server log says so once per process. Nothing else needs doing: there is no asset rebuild, and members do not need to sign in again.
Features
GET /api/stsa/registered-eventslists the signed-in participant's own registrations, each with its event, filtered byfrom/to(any event that takes place, even in part, in the window; a bare date is the whole day) and bystatus:upcoming,ongoing,checked_in,no_show,pending,withdrawn,rejected. Withdrawn and rejected registrations are listed only when asked for. It answers to a session or a token with theread:userscope, and there is no way to ask for anybody else's. See README §10.- Each registration form decides whether its registrations are listed: a new List in the events API switch on the form's STSA settings page, off by default, shown in the STSA overview. A form with no settings row lists nothing.
- An API reference for administrators. Administration → Integration → API reference shows an OpenAPI 3.1 document, generated from the running instance, of every endpoint it has — plugins included — drawn with Scalar. The page, the document and Scalar's script are all administrator-only. Scalar is vendored rather than loaded from a CDN, and the page's content security policy lets it talk to nobody but the server. See README §11.
Changes
- The plugin's blueprint no longer has an
/event/<id>prefix, since the new API is not about one event. The management URLs are unchanged. - The wheel gate (
check_wheel.py) now also requires the vendored Scalar files and refuses a wheel that carries the script in the public static folder.