Feed docsearch in prod.gcp-us-central1 (noclave and enclave) - #4874
Merged
Merged
Conversation
Add the zone endpoints of the new regional deployments of vespacloud-docsearch (default and cloud-enclave) in prod.gcp-us-central1 to all feed configs. Also restore the cloud-enclave prod.gcp-us-central1-f endpoint in _config.yml, which #4610 missed when re-enabling after #4606, and drop the stale prod.aws-euc1-az1 entry in _suggestions_reference_config.yml that #4846 left behind (it also pointed at the wrong index file). Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
thomasht86
approved these changes
Sep 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds the zone endpoints of the new regional vespacloud-docsearch deployments in prod.gcp-us-central1 (default instance
fe07fef0, cloud-enclave instanceaf7a4515) to all four feed configs. Restores the cloud-enclave prod.gcp-us-central1-f endpoint in_config.yml, which #4610 missed when re-enabling after #4606. Drops the stale prod.aws-euc1-az1 entry in_suggestions_reference_config.ymlthat #4846 left behind (it also pointed at open_index.json).Why
Both instances have been deployed to the regional GCP zone since vespa-cloud/vespa-documentation-search#268 and #269, but nothing feeds them, so those deployments hold no documents. The open_index.json feed to the GCP enclave zone has been off since March for the same reason. Matching PRs in pyvespa, sample-apps, cloud-site and blog keep the configs identical, as the comment in the files requires.