Harmonize the staging and prod services for PyPI files hosting #96
Conversation
…n staging and prod
this will allow us to re-use it for test!
|
This is ✨ almost ✨ ready, the only thing I'm concerned about is if the production and test services need different aws/gcs credentials. to be, addressed :) |
There was a problem hiding this comment.
Verified that the credentials used for Fastly to read S3 and GCS objects are the same between test-files.pythonhosted.org and files.pythonhosted.org. Also that the credentials for writing linehaul output are also shared, and that the pipelines for processing access logs are independent (aka we won't write test.pypi.org data to pypi.org's dataset).
|
In order to deploy this we'll have to deactivate the hostname on the old service before deploying. We'll throw up a status on https://status.python.org to note that test.pypi.org downloads may be temporarily impacted. |
This primarily refactors the two terraform configurations so that they're not in the same file 😂
The only actual change is renaming the friendly name of our custom VCL in the files service.
Note: The "PyPI Staging File Hosting" service in Fastly currently takes no traffic! Next step is to migrate it to :)
Towards #95