docs/expectation_gallery/2-managing-the-expectation-gallery-site.md
This should only need to be done if there are new Expectations merged in or if the content in the Expectation details pages changes (i.e. reformatting Expectation docstrings like PR 6340, PR 6423, PR 6577, and PR 8353).
Staging changes will never go to prod without doing this!
The staging S3 file will get copied to prod at <https://superconductive-public.s3.us-east-2.amazonaws.com/static/gallery/expectation_library_v2.json> and the Algolia indicies for the prod site are updated by the manual_staging_json_to_prod CI pipeline, which is only manually triggered. You can re-deploy the prod site through Netlify.
Staging site vars and Prod site vars
ALGOLIA_API_KEYALGOLIA_APPLICATION_KEYS3_EXPECTATIONS_URLS3_PACKAGES_URLThe Netlify vars are read by gatsby-node.js in the website repo
On the <https://dashboard.algolia.com/apps/2S9KBQSQ3L/indices> page, the names that match these patterns are used by the gallery
prod_expectations_*prod_expectationsprod_pack_expectations_*prod_packagesstaging_expectations_*staging_expectationsstaging_pack_expectations_*staging_packagesThese are the values of the Azure Pipelines environment variables in the pipeline yaml files which invoke the nodejs algolia scripts