BTW, the changes here are already approved for the main branch in PR #381 . We're just trying to maintain some kind of consistency between the 2 branches here.
Also, we're pretty sure that NOBODY is even calling the api code in scholarphi anymore, but IF things were to blow up, then we know to reverse this PR (for this branch or for main branch, depending on what happens).
As mentioned in preceding Deprecate partner subdomain #382 (which takes care of the
data-processing/
side), this PR is for theapi
side.BTW, the changes here are already approved for the
main
branch in PR #381 . We're just trying to maintain some kind of consistency between the 2 branches here.Also, we're pretty sure that NOBODY is even calling the
api
code in scholarphi anymore, but IF things were to blow up, then we know to reverse this PR (for this branch or formain
branch, depending on what happens).