Update KrakenD schemas

Signed-off-by: Juan Cruz Viotti <[email protected]>

Author: jviotti

DEPENDENCIES

@@ -26,7 +26,7 @@ manfred-mac-0-5 https://github.com/getmanfred/mac v0.5
 manfred-mac-0-4 https://github.com/getmanfred/mac v0.4
 manfred-mac-0-3 https://github.com/getmanfred/mac v0.3
 movielabs-omc-2-6 https://github.com/MovieLabs/OMC v2.6-release-1
-krakend https://github.com/krakend/krakend-schema 9193cfffbdce30aec18bf1f90a4cde499e9089f8
+krakend https://github.com/krakend/krakend-schema 473daa217c7a02de7e947cf682bf5ab0cffa21dc
 octue-power-curve https://github.com/octue/power-curve-schema 1.0.0.alpha-1
 usnistgov-mgi-2022-08 https://github.com/usnistgov/mgi-json-schema e5e6aaf3f5eae0d15b88ecbd57f44cc28b035f11
 cloudevents-1-0-0 https://github.com/cloudevents/spec v1.0

vendor/krakend/v2.10/endpoint_extra_config.json

@@ -127,15 +127,19 @@
         "sequential_propagated_params": {
           "title": "Sequential propagated parameters",
           "description": "The list of parameters you want to propagate from a previous response to the next request. Parameters are accessible by Lua scripts, CEL, security policies, the body generator, or plugins. When you add a `resp`-like parameter in this list, the parameter becomes available to the components mentioned in subsequent calls, **uppercasing the first letter**. For instance, if you add `resp0_user`, you can access in the second, third, etc. backends in Lua to `req:params('Resp0_user')`.The format of the parameters must start with `respX_` or `respX`, where `X` is the backend index from which you want to take the parameter. If you don't set the underscore `_`, you set the whole payload as a parameter. For instance, `resp0` sets a parameter `Resp0` to use in Lua or a Body generator and contains **the entire payload of the backend 0** (as a string). In this extreme case, you must use `no-op` in the backend's output (even the endpoint has a `json` output encoding) and you should access the value in Lua or a plugin. Note that access to **nested parameters** uses a single string with the dot notation inside, e.g.: `req_params['Resp0_f1.f2.f3']` (CEL and Security Policies), or `{{ index .req_params \"Resp0_f1.f2.f3\" }}` (body generators).\n\nSee: https://www.krakend.io/docs/endpoints/sequential-proxy/",
+          "examples": [
+            [
+              "resp0"
+            ],
+            [
+              "resp1_my_field",
+              "resp0_user_id"
+            ]
+          ],
           "type": "array",
           "items": {
             "title": "Propagated parameter name",
             "description": "A `resp`-like string that references the field you want to set a parameter and use it in the next backend call.",
-            "examples": [
-              "resp0",
-              "resp1_my_field",
-              "resp0_user_id"
-            ],
             "type": "string",
             "pattern": "^resp[0-9]+(_[^\\s]+)?$"
           }

vendor/krakend/v2.10/workflow_extra_config.json

@@ -47,6 +47,27 @@
           "default": true,
           "type": "boolean"
         },
+        "sequential_propagated_params": {
+          "$id": "#endpoint_extra_config/proxy/sequential_propagated_params",
+          "title": "Sequential propagated parameters",
+          "description": "The list of parameters you want to propagate from a previous response to the next request. Parameters are accessible by Lua scripts, CEL, security policies, the body generator, or plugins. When you add a `resp`-like parameter in this list, the parameter becomes available to the components mentioned in subsequent calls, **uppercasing the first letter**. For instance, if you add `resp0_user`, you can access in the second, third, etc. backends in Lua to `req:params('Resp0_user')`.The format of the parameters must start with `respX_` or `respX`, where `X` is the backend index from which you want to take the parameter. If you don't set the underscore `_`, you set the whole payload as a parameter. For instance, `resp0` sets a parameter `Resp0` to use in Lua or a Body generator and contains **the entire payload of the backend 0** (as a string). In this extreme case, you must use `no-op` in the backend's output (even the endpoint has a `json` output encoding) and you should access the value in Lua or a plugin. Note that access to **nested parameters** uses a single string with the dot notation inside, e.g.: `req_params['Resp0_f1.f2.f3']` (CEL and Security Policies), or `{{ index .req_params \"Resp0_f1.f2.f3\" }}` (body generators).\n\nSee: https://www.krakend.io/docs/endpoints/sequential-proxy/",
+          "examples": [
+            [
+              "resp0"
+            ],
+            [
+              "resp1_my_field",
+              "resp0_user_id"
+            ]
+          ],
+          "type": "array",
+          "items": {
+            "title": "Propagated parameter name",
+            "description": "A `resp`-like string that references the field you want to set a parameter and use it in the next backend call.",
+            "type": "string",
+            "pattern": "^resp[0-9]+(_[^\\s]+)?$"
+          }
+        },
         "static": {
           "$id": "#endpoint_extra_config/proxy/static",
           "title": "Static response",

vendor/krakend/v2.9/endpoint_extra_config.json

@@ -126,16 +126,20 @@
         },
         "sequential_propagated_params": {
           "title": "Sequential propagated parameters",
-          "description": "The list of parameters you want to propagate from a previous response to the next request. Parameters are accessible by Lua scripts, CEL, security policies, the body generator, or plugins. When you add a `resp`-like parameter in this list, the parameter becomes available to the components mentioned in subsequent calls, uppercasing the first letter. For instance, if you add `resp0_user`, you can access in the second, third, etc. backends in Lua to `req:params('Resp0_user')`.The format of the parameters must start with `respX_` or `respX`, where `X` is the backend index from which you want to take the parameter. If you don't set the underscore `_`, you set the whole payload as a parameter. For instance, `resp0` sets a parameter `Resp0` to use in Lua or a Body generator and contains **the entire payload of the backend 0** (as a string). In this extreme case, you must use `no-op` in the backend's output (even the endpoint has a `json` output encoding) and you should access the value in Lua or a plugin.",
+          "description": "The list of parameters you want to propagate from a previous response to the next request. Parameters are accessible by Lua scripts, CEL, security policies, the body generator, or plugins. When you add a `resp`-like parameter in this list, the parameter becomes available to the components mentioned in subsequent calls, **uppercasing the first letter**. For instance, if you add `resp0_user`, you can access in the second, third, etc. backends in Lua to `req:params('Resp0_user')`.The format of the parameters must start with `respX_` or `respX`, where `X` is the backend index from which you want to take the parameter. If you don't set the underscore `_`, you set the whole payload as a parameter. For instance, `resp0` sets a parameter `Resp0` to use in Lua or a Body generator and contains **the entire payload of the backend 0** (as a string). In this extreme case, you must use `no-op` in the backend's output (even the endpoint has a `json` output encoding) and you should access the value in Lua or a plugin. Note that access to **nested parameters** uses a single string with the dot notation inside, e.g.: `req_params['Resp0_f1.f2.f3']` (CEL and Security Policies), or `{{ index .req_params \"Resp0_f1.f2.f3\" }}` (body generators).\n\nSee: https://www.krakend.io/docs/endpoints/sequential-proxy/",
+          "examples": [
+            [
+              "resp0"
+            ],
+            [
+              "resp1_my_field",
+              "resp0_user_id"
+            ]
+          ],
           "type": "array",
           "items": {
             "title": "Propagated parameter name",
             "description": "A `resp`-like string that references the field you want to set a parameter and use it in the next backend call.",
-            "examples": [
-              "resp0",
-              "resp1_my_field",
-              "resp0_user_id"
-            ],
             "type": "string",
             "pattern": "^resp[0-9]+(_[^\\s]+)?$"
           }

vendor/krakend/v2.9/workflow_extra_config.json

@@ -47,6 +47,27 @@
           "default": true,
           "type": "boolean"
         },
+        "sequential_propagated_params": {
+          "$id": "#endpoint_extra_config/proxy/sequential_propagated_params",
+          "title": "Sequential propagated parameters",
+          "description": "The list of parameters you want to propagate from a previous response to the next request. Parameters are accessible by Lua scripts, CEL, security policies, the body generator, or plugins. When you add a `resp`-like parameter in this list, the parameter becomes available to the components mentioned in subsequent calls, **uppercasing the first letter**. For instance, if you add `resp0_user`, you can access in the second, third, etc. backends in Lua to `req:params('Resp0_user')`.The format of the parameters must start with `respX_` or `respX`, where `X` is the backend index from which you want to take the parameter. If you don't set the underscore `_`, you set the whole payload as a parameter. For instance, `resp0` sets a parameter `Resp0` to use in Lua or a Body generator and contains **the entire payload of the backend 0** (as a string). In this extreme case, you must use `no-op` in the backend's output (even the endpoint has a `json` output encoding) and you should access the value in Lua or a plugin. Note that access to **nested parameters** uses a single string with the dot notation inside, e.g.: `req_params['Resp0_f1.f2.f3']` (CEL and Security Policies), or `{{ index .req_params \"Resp0_f1.f2.f3\" }}` (body generators).\n\nSee: https://www.krakend.io/docs/endpoints/sequential-proxy/",
+          "examples": [
+            [
+              "resp0"
+            ],
+            [
+              "resp1_my_field",
+              "resp0_user_id"
+            ]
+          ],
+          "type": "array",
+          "items": {
+            "title": "Propagated parameter name",
+            "description": "A `resp`-like string that references the field you want to set a parameter and use it in the next backend call.",
+            "type": "string",
+            "pattern": "^resp[0-9]+(_[^\\s]+)?$"
+          }
+        },
         "static": {
           "$id": "#endpoint_extra_config/proxy/static",
           "title": "Static response",