[XDS] resolve the inconsistency treatment of parse-error vs validation-error in XDS onConfigUpdate(resources, version) API. #7508
Labels
enhancement
Feature requests. Not bugs or questions.
stale
stalebot believes this issue/PR has not been touched recently
Issue Template
Title: Fully reject (reject-all) on parse-error or PGV validation-error in the "old" CDS onConfigUpdate(resources, version) API.
Description:
In the onConfigUpdate(resources, version) function, parse-error should not be forgiven as well: we compute the to-be-removed resource names based on parsed proto's resource name, skipping a parse error means we will erroneously remove a resource.
Talked with @htuch, we'd like the impl to go back to the previous behavior: reject-all if there is any error (parse-error, PGV validation error) in the old form onConfigUpdate(resources, version) API call. And by design deltaAPI onConfigUpdate should tolerate both errors(Partial-reject).
[optional Relevant Links:]
The text was updated successfully, but these errors were encountered: