point to express processing that may be done in Gateway implementations. Some
                                examples include request or response modification, implementing
                                authentication strategies, rate-limiting, and traffic shaping. API
                                guarantee/conformance is defined based on the type of the filter.

            "in": "query",
            "name": "continue",
            "schema": {
              "type": "string",
              "uniqueItems": true
            }
          },
          {

            "in": "query",
            "name": "continue",
            "schema": {
              "type": "string",
              "uniqueItems": true
            }
          },
          {

				},
			},
			err:  "spec.affinity.nodeAffinity.requiredDuringSchedulingIgnoredDuringExecution.nodeSelectorTerms[0]: Invalid value:",
			test: "nodeAffinity modification of item in MatchExpressions not allowed",
		}, {
			old: core.Pod{
				Spec: core.PodSpec{
					Affinity: &core.Affinity{
						NodeAffinity: &core.NodeAffinity{

//
// PLEASE DO NOT MANUALLY EDIT THIS FILE!
// ONLY EXCEPTION: FIELDS THAT CANNOT BE GENERATED
//
// If you absolutely need to modify the generated fields of an op, move the op
// definition to `tf_ops.td` and perform the modification there. Generated
// fields and the process to generate them are documented at:
// mlir/tensorflow/dialectgen/README.md
//
// This file contains TensorFlow ops whose definitions are programmatically

    *   C-API functions `TF_StringDecode`, `TF_StringEncode`, and
        `TF_StringEncodedSize` are no longer relevant and have been removed; see
        `core/platform/ctstring.h` for string access/modification in C.
    *   `tensorflow.python`, `tensorflow.core` and `tensorflow.compiler` modules
        are now hidden. These modules are not part of TensorFlow public API.