Describe the bug
When a validator config is fetched by ID and passed to the run guardrails endpoint, the name field (recently added to the validator config response) is included in the payload. The run guardrails endpoint does not expect or handle this field, causing it to receive extraneous data that interferes with payload normalization and validator execution and gives us 422 validation error.
Expected behavior
The run guardrails endpoint should only receive fields required to execute the validator. The name field (and any other metadata-only fields) should be stripped from the config payload before it is forwarded, so that validator processing remains consistent regardless of what fields the config response returns.
Describe the bug
When a validator config is fetched by ID and passed to the run guardrails endpoint, the
namefield (recently added to the validator config response) is included in the payload. The run guardrails endpoint does not expect or handle this field, causing it to receive extraneous data that interferes with payload normalization and validator execution and gives us 422 validation error.Expected behavior
The run guardrails endpoint should only receive fields required to execute the validator. The
namefield (and any other metadata-only fields) should be stripped from the config payload before it is forwarded, so that validator processing remains consistent regardless of what fields the config response returns.