sh2
closed in favor of #3677
close this for now, will raise a fix if we have a clue.
This would be very helpful if we bring validations into translate, which will also help the validations in file-resources provider. For now, some validations are implemented via CEL, maybe what...
> > For now, some validations are implemented via CEL, maybe what we need to do here is to find a way convert all the CEL rules into validations code....
It seems we can take https://github.com/google/cel-go as a example, and input our CEL validation rules like: ```go ast, issues := env.Compile(`OUR-CEL-RULE`) ``` and then validate the input object like: ```go...
> oh nice @shawnh2 ! we can look into kube-builder converts CEL into `x-kubernetes-validations` fields > > https://github.com/envoyproxy/gateway/blob/cc8a86e0961e9dec5f5c56422127a8950931efb3/charts/gateway-helm/crds/generated/gateway.envoyproxy.io_backendtrafficpolicies.yaml#L218 sure we can read CEL rules from `x-kubernetes-validations` fields in all these...
Find a more suitable way to validate k8s CRD object using cel lib provided by apiextensions-apiserver. Here is an example code that works: ```go import ( "context" "math" "testing" apiextensions...
will try to first refactor the current existing k8s provider, and then implement for the new coming file provider.
still fail: https://github.com/envoyproxy/gateway/actions/runs/9655504860/job/26631669933?pr=3599#step:6:19590 cc @guydc