Update content request handling to not use just any reserved location #12876
Labels
DEV: backend
Python, databases, networking, filesystem...
P0 - critical
Priority: Release blocker or regression
TAG: tech update / debt
Change not visible to user
Milestone
Observed behavior
When a Kolibri has content requests that need processing, it may attempt to download content from KDP, now that KDP is included as a reserved network location, similarly to Studio. Originally, Studio was the only reserved location when the automatic content import feature was released.
Desired behavior
This check intends to allow Studio to be used for content import. Since that's its intent, we should just make it explicit so it avoids picking up KDP, and only bypasses the connection check if the location represents Studio.
The text was updated successfully, but these errors were encountered: