### What? As a shortcut, protect the integrations API routes via basic auth with a secret set via environment variables. ### Why? ### Initial estimate <!--X days--> ## Optional ### Additional context/supporting docs <!--E.g., a link to a heading in a spec--> ### Implementation checklist <!--Needed if this issue touches multiple systems (and if it does, consider splitting into multiple issues). See: https://notes.knowledgefutures.org/pub/7v41v2tj#implementation-checklist-suggestions.--> ### Out of Scope Later, we'll do #17 and #43 to implement a proper auth setup ### Additional notes/context/gotchas for reviewers ## Issue Readiness <!--An issue is ready when you feel it describes the work you intend to do and another team member has taken a look and signed off on it (usually, the team member who signs off will also review the PR for the project). Usually this is done for the whole project rather than issue-by-issue.-->
What?
As a shortcut, protect the integrations API routes via basic auth with a secret set via environment variables.
Why?
Initial estimate
Optional
Additional context/supporting docs
Implementation checklist
Out of Scope
Later, we'll do #17 and #43 to implement a proper auth setup
Additional notes/context/gotchas for reviewers
Issue Readiness