Currently, if the sites for the end to end tests (defined by OCW_WWW_TEST_SLUG and OCW_COURSE_TEST_SLUG) have pipelines pushed up via backpopulate_pipelines, they will be published to the public facing draft and live sites when the site is published. Instead, the test sites should only publish to the buckets defined by AWS_TEST_BUCKET_NAME and AWS_OFFLINE_TEST_BUCKET_NAME. This will mean that sites can be edited from the UI safely by any user without fear that the site will be pushed to the live site.
Plan/Design
[x] In site_pipeline.py, anywhere where S3 is interacted with, the current site should be compared against the test slug settings above. If there is a match, the site should reroute all S3 output operations to the test buckets.
[x] The functionality that filters out the test sites from all API queries should be removed.
Description/Context
Currently, if the sites for the end to end tests (defined by
OCW_WWW_TEST_SLUGandOCW_COURSE_TEST_SLUG) have pipelines pushed up viabackpopulate_pipelines, they will be published to the public facing draft and live sites when the site is published. Instead, the test sites should only publish to the buckets defined byAWS_TEST_BUCKET_NAMEandAWS_OFFLINE_TEST_BUCKET_NAME. This will mean that sites can be edited from the UI safely by any user without fear that the site will be pushed to the live site.Plan/Design
site_pipeline.py, anywhere where S3 is interacted with, the current site should be compared against the test slug settings above. If there is a match, the site should reroute all S3 output operations to the test buckets.