Allow the endpoint and deployment changes on main - #273
Merged
Merged
Conversation
Deploys have failed since #272 with "global-endpoint-change: ... does not include all of these in deployment.xml". Both #272 and #271 change the region set of the global endpoints, which Vespa refuses without an explicit override. Add global-endpoint-change for the endpoint region set, and deployment-removal for the aws-euc1-az1 deployment that #272 dropped from prod, so the removal does not fail the next validation in line. Both expire on 2026-09-30. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Contributor
Author
|
@hmusum One missing piece |
johansolbakken
approved these changes
Sep 23, 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
2 participants
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 two entries to
validation-overrides.xml, both expiring 2026-09-30:global-endpoint-changefor the changed region set of the two global endpoints, anddeployment-removalfor theaws-euc1-az1deployment that #272 dropped from prod. Nothing else changes.Why
Deploys to Vespa Cloud have failed since #272 merged, and again after #271, with
global-endpoint-change: ... does not include all of these in deployment.xml. Vespa refuses to change the region set of a live global endpoint without an explicit override, and both PRs change it. The second override is there so the removal of theaws-euc1-az1deployment does not fail the next validation in line and cost another round trip.