These 85 commits are when the Protocol Buffers files have changed:
Commit: | fa2a2cb | |
---|---|---|
Author: | nerdydread |
Added KeyID to Protobuf
Commit: | dbe5bfd | |
---|---|---|
Author: | nerdydread |
TT-8317: Add KeyID to Protobuf
Commit: | 65603cf | |
---|---|---|
Author: | Tit Petric | |
Committer: | GitHub |
[TT-12575] Synchronize release 5.3 CI state from master (source) (#6399) ### **User description** https://tyktech.atlassian.net/browse/TT-12575 This PR copies the following locations from master to LTS, updating CI state: ``` .gitignore .github/workflows/ci-tests.yml .taskfiles/ ci/tests/tracing/ coprocess/ config/Taskfile.yml apidef/oas/Taskfile.yml docker/ Dockerfile docker-compose.yml Taskfile.yml ``` coprocess/ is a documentation change, an update of the bindings was made: https://github.com/TykTechnologies/tyk/pull/6251 Expecting all tests to pass ___ ### **PR Type** enhancement, documentation ___ ### **Description** - Updated `protoc-gen-go`, `protoc`, and `protoc-gen-go-grpc` versions across multiple Go protobuf files. - Added detailed comments for struct fields in Go protobuf files. - Updated Python protobuf bindings to Protobuf Python Version 5.26.1 and simplified the generated code. - Updated Ruby protobuf bindings to use `descriptor_data` and added frozen string literal comment. ___ ### **Changes walkthrough** 📝 <table><thead><tr><th></th><th align="left">Relevant files</th></tr></thead><tbody><tr><td><strong>Enhancement</strong></td><td><details><summary>10 files</summary><table> <tr> <td> <details> <summary><strong>coprocess_session_state.pb.go</strong><dd><code>Update protobuf definitions and add comments</code> </dd></summary> <hr> coprocess/coprocess_session_state.pb.go <li>Updated <code>protoc-gen-go</code> and <code>protoc</code> versions.<br> <li> Added detailed comments for struct fields.<br> <li> Introduced new fields and deprecated some old ones.<br> </details> </td> <td><a href="https://github.com/TykTechnologies/tyk/pull/6399/files#diff-611b5735f922883f9cf41f958123bae1b8418673f537a607d0840cb191598ffd">+118/-38</a></td> </tr> <tr> <td> <details> <summary><strong>coprocess_mini_request_object.pb.go</strong><dd><code>Update protobuf definitions and add comments</code> </dd></summary> <hr> coprocess/coprocess_mini_request_object.pb.go <li>Updated <code>protoc-gen-go</code> and <code>protoc</code> versions.<br> <li> Added detailed comments for struct fields.<br> </details> </td> <td><a href="https://github.com/TykTechnologies/tyk/pull/6399/files#diff-76a073baf99408e146d81d3ddcfaf6ab4d97dca255163153f7e03cf33c69eab0">+31/-16</a> </td> </tr> <tr> <td> <details> <summary><strong>coprocess_object.pb.go</strong><dd><code>Update protobuf definitions and add comments</code> </dd></summary> <hr> coprocess/coprocess_object.pb.go <li>Updated <code>protoc-gen-go</code> and <code>protoc</code> versions.<br> <li> Added detailed comments for struct fields.<br> </details> </td> <td><a href="https://github.com/TykTechnologies/tyk/pull/6399/files#diff-3486f8360284f1db49601b71c0ec323df8819c596074f78acdeaf37340695db3">+23/-9</a> </td> </tr> <tr> <td> <details> <summary><strong>coprocess_response_object.pb.go</strong><dd><code>Update protobuf definitions and add comments</code> </dd></summary> <hr> coprocess/coprocess_response_object.pb.go <li>Updated <code>protoc-gen-go</code> and <code>protoc</code> versions.<br> <li> Added detailed comments for struct fields.<br> </details> </td> <td><a href="https://github.com/TykTechnologies/tyk/pull/6399/files#diff-6ca9b5e124a20483ca2f0ffb1280c7d5570cbd681b1a9d80e737d63d3b19d993">+17/-8</a> </td> </tr> <tr> <td> <details> <summary><strong>coprocess_common.pb.go</strong><dd><code>Update protobuf definitions and add comments</code> </dd></summary> <hr> coprocess/coprocess_common.pb.go <li>Updated <code>protoc-gen-go</code> and <code>protoc</code> versions.<br> <li> Added detailed comments for struct fields.<br> </details> </td> <td><a href="https://github.com/TykTechnologies/tyk/pull/6399/files#diff-37e6340e3fc0a6aa3f6786536531e7a656a90b07cb2d6653dde922c0ede50477">+28/-7</a> </td> </tr> <tr> <td> <details> <summary><strong>coprocess_return_overrides.pb.go</strong><dd><code>Update protobuf definitions and add comments</code> </dd></summary> <hr> coprocess/coprocess_return_overrides.pb.go <li>Updated <code>protoc-gen-go</code> and <code>protoc</code> versions.<br> <li> Added detailed comments for struct fields.<br> </details> </td> <td><a href="https://github.com/TykTechnologies/tyk/pull/6399/files#diff-049106f7788d922a634d758fea7a4f4c7a659cd40ebde102e95b7d5981ec153d">+15/-7</a> </td> </tr> <tr> <td> <details> <summary><strong>coprocess_object_grpc.pb.go</strong><dd><code>Update gRPC protobuf definitions and add comments</code> </dd></summary> <hr> coprocess/coprocess_object_grpc.pb.go <li>Updated <code>protoc-gen-go-grpc</code> and <code>protoc</code> versions.<br> <li> Added detailed comments for RPC methods.<br> </details> </td> <td><a href="https://github.com/TykTechnologies/tyk/pull/6399/files#diff-0b383295101468de421bebc6552b73e62962e60151ee56153cac3674c862ed90">+6/-2</a> </td> </tr> <tr> <td> <details> <summary><strong>coprocess_session_state_pb2.py</strong><dd><code>Update Python protobuf bindings</code> </dd></summary> <hr> coprocess/bindings/python/coprocess_session_state_pb2.py <li>Updated to Protobuf Python Version 5.26.1.<br> <li> Simplified the generated code using <code>_builder</code>.<br> </details> </td> <td><a href="https://github.com/TykTechnologies/tyk/pull/6399/files#diff-1272bb7e59c24600bac5c530ce6a79a4c1471be262d9712c622132f69ad7f9e6">+37/-647</a></td> </tr> <tr> <td> <details> <summary><strong>coprocess_session_state_pb2.py</strong><dd><code>Update Python protobuf bindings</code> </dd></summary> <hr> coprocess/python/proto/coprocess_session_state_pb2.py <li>Updated to Protobuf Python Version 5.26.1.<br> <li> Simplified the generated code using <code>_builder</code>.<br> </details> </td> <td><a href="https://github.com/TykTechnologies/tyk/pull/6399/files#diff-0cb388bb5c8b1927163cf3f0858d46266bc68f17df1dcc62f40e14f011df9f38">+37/-647</a></td> </tr> <tr> <td> <details> <summary><strong>coprocess_response_object_pb.rb</strong><dd><code>Update Ruby protobuf bindings</code> </dd></summary> <hr> coprocess/bindings/ruby/coprocess_response_object_pb.rb <li>Updated the generated code to use <code>descriptor_data</code>.<br> <li> Added frozen string literal comment.<br> </details> </td> <td><a href="https://github.com/TykTechnologies/tyk/pull/6399/files#diff-875ee9bcacb60539cc81f7676e60e5ed73fcaadcf094e95e69d6f0d6cd095997">+8/-15</a> </td> </tr> </table></details></td></tr><tr><td><strong>Additional files (token-limit)</strong></td><td><details><summary>38 files</summary><table> <tr> <td> <details> <summary><strong>coprocess_mini_request_object_pb2.py</strong><dd><code>...</code> </dd></summary> <hr> coprocess/bindings/python/coprocess_mini_request_object_pb2.py ... </details> </td> <td><a href="https://github.com/TykTechnologies/tyk/pull/6399/files#diff-412221f231bbc1bc1b55a9cebe883d06bd2a3bf7f1b0b0cc127e5b18be9def48">+35/-391</a></td> </tr> <tr> <td> <details> <summary><strong>coprocess_mini_request_object_pb2.py</strong><dd><code>...</code> </dd></summary> <hr> coprocess/python/proto/coprocess_mini_request_object_pb2.py ... </details> </td> <td><a href="https://github.com/TykTechnologies/tyk/pull/6399/files#diff-49e17ba2d6c9553dc6f88d309da2656f9cb756c7e0bb68be23ecaacd4427bf28">+35/-391</a></td> </tr> <tr> <td> <details> <summary><strong>coprocess_object_pb2.py</strong><dd><code>...</code> </dd></summary> <hr> coprocess/bindings/python/coprocess_object_pb2.py ... </details> </td> <td><a href="https://github.com/TykTechnologies/tyk/pull/6399/files#diff-a6b9eab22b2b5d5e967db957d94460876733862f175d45c24e4c4931bff2a1c5">+28/-305</a></td> </tr> <tr> <td> <details> <summary><strong>coprocess_object_pb2.py</strong><dd><code>...</code> </dd></summary> <hr> coprocess/python/proto/coprocess_object_pb2.py ... </details> </td> <td><a href="https://github.com/TykTechnologies/tyk/pull/6399/files#diff-fe9a0e698d677a7f82407f690abfa1a5393b73bf8ee0098dffe9af4c4c724b0c">+28/-305</a></td> </tr> <tr> <td> <details> <summary><strong>coprocess_response_object_pb2.py</strong><dd><code>...</code> </dd></summary> <hr> coprocess/bindings/python/coprocess_response_object_pb2.py ... </details> </td> <td><a href="https://github.com/TykTechnologies/tyk/pull/6399/files#diff-6bf1bccef4f1daa262af78b92d5d645c3c2a4a3f0707d54f32cd7e8ab7bf38b7">+20/-180</a></td> </tr> <tr> <td> <details> <summary><strong>coprocess_response_object_pb2.py</strong><dd><code>...</code> </dd></summary> <hr> coprocess/python/proto/coprocess_response_object_pb2.py ... </details> </td> <td><a href="https://github.com/TykTechnologies/tyk/pull/6399/files#diff-06ee8b18e7ffe18fbf6be58eddcf7776f01b4b0ad8a97ca288c15d64005f2a12">+20/-180</a></td> </tr> <tr> <td> <details> <summary><strong>coprocess_return_overrides_pb2.py</strong><dd><code>...</code> </dd></summary> <hr> coprocess/bindings/python/coprocess_return_overrides_pb2.py ... </details> </td> <td><a href="https://github.com/TykTechnologies/tyk/pull/6399/files#diff-7d414ef098386e69160616d59ef89b68497bbf14ebcc8a8906f2837f457fd1f0">+18/-133</a></td> </tr> <tr> <td> <details> <summary><strong>coprocess_return_overrides_pb2.py</strong><dd><code>...</code> </dd></summary> <hr> coprocess/python/proto/coprocess_return_overrides_pb2.py ... </details> </td> <td><a href="https://github.com/TykTechnologies/tyk/pull/6399/files#diff-622616a4a47396aa12650230332d64a7590377a0bd13cbfde59d2dfdd45d6011">+18/-133</a></td> </tr> <tr> <td> <details> <summary><strong>coprocess_object_pb2_grpc.py</strong><dd><code>...</code> </dd></summary> <hr> coprocess/bindings/python/coprocess_object_pb2_grpc.py ... </details> </td> <td><a href="https://github.com/TykTechnologies/tyk/pull/6399/files#diff-67c8e4abacb5ea853ee73efcb8e2635b71625097973d46a75cc23e94f325497a">+133/-46</a></td> </tr> <tr> <td> <details> <summary><strong>coprocess_object_pb2_grpc.py</strong><dd><code>...</code> </dd></summary> <hr> coprocess/python/proto/coprocess_object_pb2_grpc.py ... </details> </td> <td><a href="https://github.com/TykTechnologies/tyk/pull/6399/files#diff-a1e3299fb7af1a3dc48737936d2299f9204ed0754b0d3d97f662478e875d0b15">+133/-46</a></td> </tr> <tr> <td> <details> <summary><strong>coprocess_common_pb2.py</strong><dd><code>...</code> </dd></summary> <hr> coprocess/bindings/python/coprocess_common_pb2.py ... </details> </td> <td><a href="https://github.com/TykTechnologies/tyk/pull/6399/files#diff-bf69aa40323fa48acebafd0377e68b2cfced9d6f1b73b9fcd01a2f209e972c5b">+16/-104</a></td> </tr> <tr> <td> <details> <summary><strong>coprocess_common_pb2.py</strong><dd><code>...</code> </dd></summary> <hr> coprocess/python/proto/coprocess_common_pb2.py ... </details> </td> <td><a href="https://github.com/TykTechnologies/tyk/pull/6399/files#diff-cc40fde101363986b19fa0fa68217889075a0b8b5d9d2d7651d6ffaf0e77d846">+16/-104</a></td> </tr> <tr> <td> <details> <summary><strong>coprocess_session_state_pb.rb</strong><dd><code>...</code> </dd></summary> <hr> coprocess/bindings/ruby/coprocess_session_state_pb.rb ... </details> </td> <td><a href="https://github.com/TykTechnologies/tyk/pull/6399/files#diff-dad9073038e2631ac0180f3f6b8afe0eb44481763f3964fa81528d9b24304ca3">+12/-61</a> </td> </tr> <tr> <td> <details> <summary><strong>coprocess_mini_request_object_pb.rb</strong><dd><code>...</code> </dd></summary> <hr> coprocess/bindings/ruby/coprocess_mini_request_object_pb.rb ... </details> </td> <td><a href="https://github.com/TykTechnologies/tyk/pull/6399/files#diff-2b21bf715f10345cf1fcf9c6c007aadedb51b6139e5f53caaf4c9f27c73ff64a">+8/-19</a> </td> </tr> <tr> <td> <details> <summary><strong>coprocess_object_pb.rb</strong><dd><code>...</code> </dd></summary> <hr> coprocess/bindings/ruby/coprocess_object_pb.rb ... </details> </td> <td><a href="https://github.com/TykTechnologies/tyk/pull/6399/files#diff-3536bb4df1845c54f83ee6ab65cb91fae63cfe1b39a52345459e54a8eec5d982">+10/-19</a> </td> </tr> <tr> <td> <details> <summary><strong>coprocess_common_pb.rb</strong><dd><code>...</code> </dd></summary> <hr> coprocess/bindings/ruby/coprocess_common_pb.rb ... </details> </td> <td><a href="https://github.com/TykTechnologies/tyk/pull/6399/files#diff-fdae040d9415497f766846bbc27a88ada8b6376465e0831b700b69d9eafc9dc5">+8/-15</a> </td> </tr> <tr> <td> <details> <summary><strong>coprocess_return_overrides_pb.rb</strong><dd><code>...</code> </dd></summary> <hr> coprocess/bindings/ruby/coprocess_return_overrides_pb.rb ... </details> </td> <td><a href="https://github.com/TykTechnologies/tyk/pull/6399/files#diff-9483399b2d58af6fb52b18a7fb70aefeb1f69664ca2bd8fd79c4b58d3203ef86">+7/-10</a> </td> </tr> <tr> <td> <details> <summary><strong>coprocess_session_state.proto</strong><dd><code>...</code> </dd></summary> <hr> coprocess/proto/coprocess_session_state.proto ... </details> </td> <td><a href="https://github.com/TykTechnologies/tyk/pull/6399/files#diff-52d9bd81d6a15710cda9c8fb188965225acdc731c1e67e5252ee07e0d2664117">+105/-0</a> </td> </tr> <tr> <td> <details> <summary><strong>docker-compose.yml</strong><dd><code>...</code> </dd></summary> <hr> ci/tests/tracing/docker-compose.yml ... </details> </td> <td><a href="https://github.com/TykTechnologies/tyk/pull/6399/files#diff-ca0b13836790f0db90a490b5000a738787f3d5d839313d456ec9f94b33dac7ee">+128/-126</a></td> </tr> <tr> <td> <details> <summary><strong>ci-tests.yml</strong><dd><code>...</code> </dd></summary> <hr> .github/workflows/ci-tests.yml ... </details> </td> <td><a href="https://github.com/TykTechnologies/tyk/pull/6399/files#diff-03609cb60b0c6e92fb771eb8787d6722b8c31ca4c03eabc788e147acd8c6fb43">+45/-41</a> </td> </tr> <tr> <td> <details> <summary><strong>test.yml</strong><dd><code>...</code> </dd></summary> <hr> .taskfiles/test.yml ... </details> </td> <td><a href="https://github.com/TykTechnologies/tyk/pull/6399/files#diff-f1fbe7f7f14888019b8845634ed008e1c43f6e5a5c0b2707336fc7f8e15a36fb">+116/-0</a> </td> </tr> <tr> <td> <details> <summary><strong>Taskfile.yml</strong><dd><code>...</code> </dd></summary> <hr> ci/tests/tracing/Taskfile.yml ... </details> </td> <td><a href="https://github.com/TykTechnologies/tyk/pull/6399/files#diff-d7d2dd36087d885290fa602e3e810f648e36c0ebf71becf09fcd68e73371ac96">+55/-0</a> </td> </tr> <tr> <td> <details> <summary><strong>Taskfile.yml</strong><dd><code>...</code> </dd></summary> <hr> Taskfile.yml ... </details> </td> <td><a href="https://github.com/TykTechnologies/tyk/pull/6399/files#diff-cd2d359855d0301ce190f1ec3b4c572ea690c83747f6df61c9340720e3d2425e">+11/-3</a> </td> </tr> <tr> <td> <details> <summary><strong>coprocess_common.proto</strong><dd><code>...</code> </dd></summary> <hr> coprocess/proto/coprocess_common.proto ... </details> </td> <td><a href="https://github.com/TykTechnologies/tyk/pull/6399/files#diff-17a800d3b7dcb11fe7e086089442f1fb35f10f7b541136a4263afc747dadea07">+30/-1</a> </td> </tr> <tr> <td> <details> <summary><strong>Taskfile.yml</strong><dd><code>...</code> </dd></summary> <hr> coprocess/proto/Taskfile.yml ... </details> </td> <td><a href="https://github.com/TykTechnologies/tyk/pull/6399/files#diff-63c4bcd2503d34a284927b705634398d59d13d530819d11bc7fcc6482eefb730">+26/-3</a> </td> </tr> <tr> <td> <details> <summary><strong>coprocess_mini_request_object.proto</strong><dd><code>...</code> </dd></summary> <hr> coprocess/proto/coprocess_mini_request_object.proto ... </details> </td> <td><a href="https://github.com/TykTechnologies/tyk/pull/6399/files#diff-716bb2f344af9e1c472a6f7cf4210441db08c20adf098eb6a0868151290201ed">+28/-0</a> </td> </tr> <tr> <td> <details> <summary><strong>coprocess_object.proto</strong><dd><code>...</code> </dd></summary> <hr> coprocess/proto/coprocess_object.proto ... </details> </td> <td><a href="https://github.com/TykTechnologies/tyk/pull/6399/files#diff-e18abe4c58628cc8087e16ab47d3d78788a1416cbe905c7613aff6f168e19d4e">+26/-0</a> </td> </tr> <tr> <td> <details> <summary><strong>Taskfile.yml</strong><dd><code>...</code> </dd></summary> <hr> ci/tests/tracing/tracetest/Taskfile.yml ... </details> </td> <td><a href="https://github.com/TykTechnologies/tyk/pull/6399/files#diff-1ea785f38e54f75865fed6e19e96dff08ba102c80a3e438ae2e7d54b8e435af2">+12/-5</a> </td> </tr> <tr> <td> <details> <summary><strong>Taskfile.yml</strong><dd><code>...</code> </dd></summary> <hr> coprocess/Taskfile.yml ... </details> </td> <td><a href="https://github.com/TykTechnologies/tyk/pull/6399/files#diff-3570989f97390bd8441ef414dffdefb7dd0b29bfa6f01e413c68cc51a3f68485">+36/-0</a> </td> </tr> <tr> <td> <details> <summary><strong>coprocess_response_object.proto</strong><dd><code>...</code> </dd></summary> <hr> coprocess/proto/coprocess_response_object.proto ... </details> </td> <td><a href="https://github.com/TykTechnologies/tyk/pull/6399/files#diff-7fb11ae1b2be3be2aadda9bbc9860ef8729addaf6fbabf2fe8d4455b2dea6bc0">+16/-0</a> </td> </tr> <tr> <td> <details> <summary><strong>collector.config.yml</strong><dd><code>...</code> </dd></summary> <hr> ci/tests/tracing/configs/otelcollector/collector.config.yml ... </details> </td> <td><a href="https://github.com/TykTechnologies/tyk/pull/6399/files#diff-7ed5aea20a5cf1666f7de8ed60b105467e4a6be7a137d5c145e58f772803b690">+22/-20</a> </td> </tr> <tr> <td> <details> <summary><strong>Taskfile.yml</strong><dd><code>...</code> </dd></summary> <hr> .taskfiles/deps/Taskfile.yml ... </details> </td> <td><a href="https://github.com/TykTechnologies/tyk/pull/6399/files#diff-bd2d25e8a19db2d54ea34295acdc50b5402b7469eaf3e16b083f3e66dbe4fd9d">+11/-6</a> </td> </tr> <tr> <td> <details> <summary><strong>coprocess_return_overrides.proto</strong><dd><code>...</code> </dd></summary> <hr> coprocess/proto/coprocess_return_overrides.proto ... </details> </td> <td><a href="https://github.com/TykTechnologies/tyk/pull/6399/files#diff-7d49b86e4f4fef6d30ddb0c48023ba6504181d3356d4bbb71e9a1ffba2c08a05">+13/-0</a> </td> </tr> <tr> <td> <details> <summary><strong>docker-compose.yml</strong><dd><code>...</code> </dd></summary> <hr> docker-compose.yml ... </details> </td> <td><a href="https://github.com/TykTechnologies/tyk/pull/6399/files#diff-e45e45baeda1c1e73482975a664062aa56f20c03dd9d64a827aba57775bed0d3">+6/-7</a> </td> </tr> <tr> <td> <details> <summary><strong>tyk.env</strong><dd><code>...</code> </dd></summary> <hr> ci/tests/tracing/configs/tyk.env ... </details> </td> <td><a href="https://github.com/TykTechnologies/tyk/pull/6399/files#diff-69098dd1c6ed48bb914d7d4534673f9f42d146b7ecf37fda7c494886215bea1c">+3/-1</a> </td> </tr> <tr> <td> <details> <summary><strong>httpbin.yml</strong><dd><code>...</code> </dd></summary> <hr> docker/services/httpbin.yml ... </details> </td> <td><a href="https://github.com/TykTechnologies/tyk/pull/6399/files#diff-1a1b1d8bf4798076a41ca5f3bba0d465dc387e58b6593adbb28a4d5fe60eb810">+15/-0</a> </td> </tr> <tr> <td> <details> <summary><strong>redis.yml</strong><dd><code>...</code> </dd></summary> <hr> docker/services/redis.yml ... </details> </td> <td><a href="https://github.com/TykTechnologies/tyk/pull/6399/files#diff-8a7e423c83c2749144ba2aee0af3f9ec281926c7b8a6ae00737088687206708a">+1/-1</a> </td> </tr> <tr> <td> <details> <summary><strong>docker-compose.yml</strong><dd><code>...</code> </dd></summary> <hr> docker/services/docker-compose.yml ... </details> </td> <td><a href="https://github.com/TykTechnologies/tyk/pull/6399/files#diff-8ce9686535a65153456ca4275ee4902069de9180063082f0d35f367b7c86f040">+1/-0</a> </td> </tr> </table></details></td></tr></tr></tbody></table> ___ > 💡 **PR-Agent usage**: >Comment `/help` on the PR to get a list of all available PR-Agent tools and their descriptions --------- Co-authored-by: Tit Petric <tit@tyk.io>
The documentation is generated from this commit.
Commit: | 656095e | |
---|---|---|
Author: | dcs3spp | |
Committer: | GitHub |
[DX-1084] Add documentation to protobuf source code files for review (#6251) [DX-1084](https://tyktech.atlassian.net/browse/DX-1084) ## Description - Added documentation for protobuf messages and service for review - Task file has been updated to use a Python virtual environment. - The PR includes the bindings regenerated - The PR is large and has 22 files that includes the comments in the regenerated bindings. If required I can include just the protobuf files and then once reviewed include a separate PR for the bindings? ## Related Issue <!-- This project only accepts pull requests related to open issues. --> <!-- If suggesting a new feature or change, please discuss it in an issue first. --> <!-- If fixing a bug, there should be an issue describing it with steps to reproduce. --> <!-- OSS: Please link to the issue here. Tyk: please create/link the JIRA ticket. --> ## Motivation and Context <!-- Why is this change required? What problem does it solve? --> ## How This Has Been Tested <!-- Please describe in detail how you tested your changes --> <!-- Include details of your testing environment, and the tests --> <!-- you ran to see how your change affects other areas of the code, etc. --> <!-- This information is helpful for reviewers and QA. --> ## Screenshots (if appropriate) ## Types of changes <!-- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [x] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) - [x] Refactoring or add test (improvements in base code or adds test coverage to functionality) ## Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply --> <!-- If there are no documentation updates required, mark the item as checked. --> <!-- Raise up any additional concerns not covered by the checklist. --> - [x] I ensured that the documentation is up to date - [ ] I explained why this PR updates go.mod in detail with reasoning why it's required - [ ] I would like a code coverage CI quality gate exception and have explained why [DX-1084]: https://tyktech.atlassian.net/browse/DX-1084?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ --------- Co-authored-by: Simon Pears <simon@tyk.io> Co-authored-by: Tit Petric <tit@tyk.io>
The documentation is generated from this commit.
Commit: | e8fa6cd | |
---|---|---|
Author: | Simon Pears |
Fix comment styling
Commit: | 38dbd76 | |
---|---|---|
Author: | Simon Pears |
Update list of string to include brief in description
Commit: | 774d29a | |
---|---|---|
Author: | Simon Pears |
Update protbuf files to fix render issues
Commit: | 81ed0ad | |
---|---|---|
Author: | Simon Pears |
Update hashing algorithms for basic auth
Commit: | c5ba6ae | |
---|---|---|
Author: | Simon Pears |
doxygen coprocess_session_state.proto
Commit: | 09e2b22 | |
---|---|---|
Author: | Simon Pears |
doxygen return_overrides.proto
Commit: | f2d01c4 | |
---|---|---|
Author: | Simon Pears |
doxygen response_object
Commit: | 466228a | |
---|---|---|
Author: | Simon Pears |
doxygen object
Commit: | 221d30d | |
---|---|---|
Author: | Simon Pears |
doxygen mini_request_object
Commit: | 64cf438 | |
---|---|---|
Author: | Simon Pears |
update doxygen custom auth hook description
Commit: | cef9c72 | |
---|---|---|
Author: | Simon Pears |
doxygen update UnknownPlugin
Commit: | aa86f84 | |
---|---|---|
Author: | Simon Pears |
doxygen comments
Commit: | 9228a29 | |
---|---|---|
Author: | Leonid Bugaev | |
Committer: | GitHub |
Merging to release-5-lts: TT-851 update proto binding script (#5173) TT-851 update proto binding script (#5173) <!-- Provide a general summary of your changes in the Title above --> ## Description In order to fix the issue reported in TT-851 it was necessary to modify the structure of how the headers are stored and passed to the response middlewares, it happens that one header can have multiple values (Eg: Set-Cookie header) and the gateway currently considers only one value per header. So, this PR contains: - Update of the protobuf files and added a new field to handle the Headers, this is a repeated value instead a string and its name is `multivalue_headers`. - Update of the update-bindings.sh script - Updated the bindings for go, python, ruby - Updated the code in gateway/coprocess.go to work with headers represented as Key => []Values Is good to mention that now the object passed to the middleware contains the old format header (one key - one value) and the new format header (the mutivalue headers: one key- multiple values). So: - If a new header is added in the old field, then this will be added as well in the new field - If a header is removed from the old field, then it will be removed as well in the new field - If a value of a header is updated then it will overwritte all the values for that header in the new field. In the end, the new field is the one being used to put all the headers back in the response, because after calling the middleware a synchronization process of headers is executed just to ensure that all the changes are replicated in the new field, therefore, all the values for every header are transmitted to the end user. ## Related Issue https://tyktech.atlassian.net/browse/TT-851 These are the changes of https://github.com/TykTechnologies/tyk/pull/5140 but segmented into multiple smaller PRs. Children PRs: - https://github.com/TykTechnologies/tyk/pull/5174 - https://github.com/TykTechnologies/tyk/pull/5175 ## Motivation and Context <!-- Why is this change required? What problem does it solve? --> ## How This Has Been Tested - Follow replication steps in the jira ticket ## Screenshots (if appropriate) ## Types of changes <!-- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) - [ ] Refactoring or add test (improvements in base code or adds test coverage to functionality) ## Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply --> <!-- If there are no documentation updates required, mark the item as checked. --> <!-- Raise up any additional concerns not covered by the checklist. --> - [ ] I ensured that the documentation is up to date - [ ] I explained why this PR updates go.mod in detail with reasoning why it's required - [ ] I would like a code coverage CI quality gate exception and have explained why
Commit: | 6bb214c | |
---|---|---|
Author: | Leonid Bugaev | |
Committer: | GitHub |
Merging to release-5.1: TT-851 update proto binding script (#5173) TT-851 update proto binding script (#5173) <!-- Provide a general summary of your changes in the Title above --> ## Description In order to fix the issue reported in TT-851 it was necessary to modify the structure of how the headers are stored and passed to the response middlewares, it happens that one header can have multiple values (Eg: Set-Cookie header) and the gateway currently considers only one value per header. So, this PR contains: - Update of the protobuf files and added a new field to handle the Headers, this is a repeated value instead a string and its name is `multivalue_headers`. - Update of the update-bindings.sh script - Updated the bindings for go, python, ruby - Updated the code in gateway/coprocess.go to work with headers represented as Key => []Values Is good to mention that now the object passed to the middleware contains the old format header (one key - one value) and the new format header (the mutivalue headers: one key- multiple values). So: - If a new header is added in the old field, then this will be added as well in the new field - If a header is removed from the old field, then it will be removed as well in the new field - If a value of a header is updated then it will overwritte all the values for that header in the new field. In the end, the new field is the one being used to put all the headers back in the response, because after calling the middleware a synchronization process of headers is executed just to ensure that all the changes are replicated in the new field, therefore, all the values for every header are transmitted to the end user. ## Related Issue https://tyktech.atlassian.net/browse/TT-851 These are the changes of https://github.com/TykTechnologies/tyk/pull/5140 but segmented into multiple smaller PRs. Children PRs: - https://github.com/TykTechnologies/tyk/pull/5174 - https://github.com/TykTechnologies/tyk/pull/5175 ## Motivation and Context <!-- Why is this change required? What problem does it solve? --> ## How This Has Been Tested - Follow replication steps in the jira ticket ## Screenshots (if appropriate) ## Types of changes <!-- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) - [ ] Refactoring or add test (improvements in base code or adds test coverage to functionality) ## Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply --> <!-- If there are no documentation updates required, mark the item as checked. --> <!-- Raise up any additional concerns not covered by the checklist. --> - [ ] I ensured that the documentation is up to date - [ ] I explained why this PR updates go.mod in detail with reasoning why it's required - [ ] I would like a code coverage CI quality gate exception and have explained why
Commit: | b4eeccd | |
---|---|---|
Author: | Leonid Bugaev | |
Committer: | GitHub |
Merging to release-5.1.0: TT-851 update proto binding script (#5173) TT-851 update proto binding script (#5173) <!-- Provide a general summary of your changes in the Title above --> ## Description In order to fix the issue reported in TT-851 it was necessary to modify the structure of how the headers are stored and passed to the response middlewares, it happens that one header can have multiple values (Eg: Set-Cookie header) and the gateway currently considers only one value per header. So, this PR contains: - Update of the protobuf files and added a new field to handle the Headers, this is a repeated value instead a string and its name is `multivalue_headers`. - Update of the update-bindings.sh script - Updated the bindings for go, python, ruby - Updated the code in gateway/coprocess.go to work with headers represented as Key => []Values Is good to mention that now the object passed to the middleware contains the old format header (one key - one value) and the new format header (the mutivalue headers: one key- multiple values). So: - If a new header is added in the old field, then this will be added as well in the new field - If a header is removed from the old field, then it will be removed as well in the new field - If a value of a header is updated then it will overwritte all the values for that header in the new field. In the end, the new field is the one being used to put all the headers back in the response, because after calling the middleware a synchronization process of headers is executed just to ensure that all the changes are replicated in the new field, therefore, all the values for every header are transmitted to the end user. ## Related Issue https://tyktech.atlassian.net/browse/TT-851 These are the changes of https://github.com/TykTechnologies/tyk/pull/5140 but segmented into multiple smaller PRs. Children PRs: - https://github.com/TykTechnologies/tyk/pull/5174 - https://github.com/TykTechnologies/tyk/pull/5175 ## Motivation and Context <!-- Why is this change required? What problem does it solve? --> ## How This Has Been Tested - Follow replication steps in the jira ticket ## Screenshots (if appropriate) ## Types of changes <!-- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) - [ ] Refactoring or add test (improvements in base code or adds test coverage to functionality) ## Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply --> <!-- If there are no documentation updates required, mark the item as checked. --> <!-- Raise up any additional concerns not covered by the checklist. --> - [ ] I ensured that the documentation is up to date - [ ] I explained why this PR updates go.mod in detail with reasoning why it's required - [ ] I would like a code coverage CI quality gate exception and have explained why
Commit: | ef42277 | |
---|---|---|
Author: | Sredny M | |
Committer: | GitHub |
TT-851 update proto binding script (#5173) <!-- Provide a general summary of your changes in the Title above --> ## Description In order to fix the issue reported in TT-851 it was necessary to modify the structure of how the headers are stored and passed to the response middlewares, it happens that one header can have multiple values (Eg: Set-Cookie header) and the gateway currently considers only one value per header. So, this PR contains: - Update of the protobuf files and added a new field to handle the Headers, this is a repeated value instead a string and its name is `multivalue_headers`. - Update of the update-bindings.sh script - Updated the bindings for go, python, ruby - Updated the code in gateway/coprocess.go to work with headers represented as Key => []Values Is good to mention that now the object passed to the middleware contains the old format header (one key - one value) and the new format header (the mutivalue headers: one key- multiple values). So: - If a new header is added in the old field, then this will be added as well in the new field - If a header is removed from the old field, then it will be removed as well in the new field - If a value of a header is updated then it will overwritte all the values for that header in the new field. In the end, the new field is the one being used to put all the headers back in the response, because after calling the middleware a synchronization process of headers is executed just to ensure that all the changes are replicated in the new field, therefore, all the values for every header are transmitted to the end user. ## Related Issue https://tyktech.atlassian.net/browse/TT-851 These are the changes of https://github.com/TykTechnologies/tyk/pull/5140 but segmented into multiple smaller PRs. Children PRs: - https://github.com/TykTechnologies/tyk/pull/5174 - https://github.com/TykTechnologies/tyk/pull/5175 ## Motivation and Context <!-- Why is this change required? What problem does it solve? --> ## How This Has Been Tested - Follow replication steps in the jira ticket ## Screenshots (if appropriate) ## Types of changes <!-- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) - [ ] Refactoring or add test (improvements in base code or adds test coverage to functionality) ## Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply --> <!-- If there are no documentation updates required, mark the item as checked. --> <!-- Raise up any additional concerns not covered by the checklist. --> - [ ] I ensured that the documentation is up to date - [ ] I explained why this PR updates go.mod in detail with reasoning why it's required - [ ] I would like a code coverage CI quality gate exception and have explained why
Commit: | be71408 | |
---|---|---|
Author: | JRWu |
Regenerating protobufs and updating with the correct package naming for coprocess from update_bindings.sh
Commit: | 41529e6 | |
---|---|---|
Author: | JRWu |
Updating with preliminary work on extending the gRPC Session State object to include KeyID and KeyHash
Commit: | ddac063 | |
---|---|---|
Author: | Tit Petric |
Add taskfile and example proto file for middlewares
Commit: | 1adc29c | |
---|---|---|
Author: | Tit Petric | |
Committer: | Tit Petric |
Update broken .proto files, add go_package option, source_relative build
Commit: | 45e3ff6 | |
---|---|---|
Author: | Matias Insaurralde |
proto: remove unused import and clear latest protoc warning
Commit: | 116427d | |
---|---|---|
Author: | gernest |
move pubsub to external service
Commit: | d380efe | |
---|---|---|
Author: | gernest |
add analytics
Commit: | 97e0d9e | |
---|---|---|
Author: | gernest |
add PubSub
Commit: | c6acec5 | |
---|---|---|
Author: | Leonid Bugaev | |
Committer: | Leonid Bugaev |
Go 1.5 migration (#3454) Go 1.4 introduced TLS 1.3 by default, which we can't do since a lot of our clients depend on 1.2. In order to disable 1.3 Go added new `MaxVersion` option to `tls.Config` structure. For example one of 1.3 breaking "features" is the inability to explicitly set TLS ciphers (in 1.3 they should be picked automatically), and a lot of enterprises depend on it. In order to make it non-breaking change I added new max SSL version attributes to all needed sections (everywhere where there is min version), and it is set to 1.2 by default. New config fields: `http_server_options.max_version` `proxy_ssl_max_version` Api definition fields: `proxy.transport.ssl_max_version` Additionally, fixed a bunch of tests (not related to 1.5 change from what I see). All the vendoring removed as well! As part of QA we need to ensure that all outbound and inbound Gateway calls use TLS 1.2, which includes: - [ ] Uptime tests - [ ] JSVM HTTP calls - [ ] Batch API - [ ] Reverse proxy - [ ] Gateway -> Dashboard communication - [ ] Gateway -> MDCB communication - [ ] UDG GraphQL and JSON data sources <!-- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [x] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) - [ ] Refactoring or add test (improvements in base code or adds test coverage to functionality) <!-- Go over all the following points, and put an `x` in all the boxes that apply --> <!-- If you're unsure about any of these, don't hesitate to ask; we're here to help! --> - [x] Make sure you are requesting to **pull a topic/feature/bugfix branch** (right side). If pulling from your own fork, don't request your `master`! - [x] Make sure you are making a pull request against the **`master` branch** (left side). Also, you should start *your branch* off *our latest `master`*. - [x] My change requires a change to the documentation. - [ ] If you've changed APIs, describe what needs to be updated in the documentation. - [ ] If new config option added, ensure that it can be set via ENV variable - [ ] I have updated the documentation accordingly. - [x] Modules and vendor dependencies have been updated; run `go mod tidy && go mod vendor` - [ ] When updating library version must provide reason/explanation for this update. - [x] I have added tests to cover my changes. - [x] All new and existing tests passed. - [x] Check your code additions will not fail linting checks: - [x] `go fmt -s` - [x] `go vet`
Commit: | 0400d49 | |
---|---|---|
Author: | Leonid Bugaev | |
Committer: | Leonid Bugaev |
Go 1.5 migration (#3454) Go 1.4 introduced TLS 1.3 by default, which we can't do since a lot of our clients depend on 1.2. In order to disable 1.3 Go added new `MaxVersion` option to `tls.Config` structure. For example one of 1.3 breaking "features" is the inability to explicitly set TLS ciphers (in 1.3 they should be picked automatically), and a lot of enterprises depend on it. In order to make it non-breaking change I added new max SSL version attributes to all needed sections (everywhere where there is min version), and it is set to 1.2 by default. New config fields: `http_server_options.max_version` `proxy_ssl_max_version` Api definition fields: `proxy.transport.ssl_max_version` Additionally, fixed a bunch of tests (not related to 1.5 change from what I see). All the vendoring removed as well! As part of QA we need to ensure that all outbound and inbound Gateway calls use TLS 1.2, which includes: - [ ] Uptime tests - [ ] JSVM HTTP calls - [ ] Batch API - [ ] Reverse proxy - [ ] Gateway -> Dashboard communication - [ ] Gateway -> MDCB communication - [ ] UDG GraphQL and JSON data sources <!-- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [x] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) - [ ] Refactoring or add test (improvements in base code or adds test coverage to functionality) <!-- Go over all the following points, and put an `x` in all the boxes that apply --> <!-- If you're unsure about any of these, don't hesitate to ask; we're here to help! --> - [x] Make sure you are requesting to **pull a topic/feature/bugfix branch** (right side). If pulling from your own fork, don't request your `master`! - [x] Make sure you are making a pull request against the **`master` branch** (left side). Also, you should start *your branch* off *our latest `master`*. - [x] My change requires a change to the documentation. - [ ] If you've changed APIs, describe what needs to be updated in the documentation. - [ ] If new config option added, ensure that it can be set via ENV variable - [ ] I have updated the documentation accordingly. - [x] Modules and vendor dependencies have been updated; run `go mod tidy && go mod vendor` - [ ] When updating library version must provide reason/explanation for this update. - [x] I have added tests to cover my changes. - [x] All new and existing tests passed. - [x] Check your code additions will not fail linting checks: - [x] `go fmt -s` - [x] `go vet`
Commit: | 8ec9903 | |
---|---|---|
Author: | Leonid Bugaev | |
Committer: | GitHub |
Go 1.5 migration (#3454) Go 1.4 introduced TLS 1.3 by default, which we can't do since a lot of our clients depend on 1.2. In order to disable 1.3 Go added new `MaxVersion` option to `tls.Config` structure. For example one of 1.3 breaking "features" is the inability to explicitly set TLS ciphers (in 1.3 they should be picked automatically), and a lot of enterprises depend on it. In order to make it non-breaking change I added new max SSL version attributes to all needed sections (everywhere where there is min version), and it is set to 1.2 by default. New config fields: `http_server_options.max_version` `proxy_ssl_max_version` Api definition fields: `proxy.transport.ssl_max_version` Additionally, fixed a bunch of tests (not related to 1.5 change from what I see). All the vendoring removed as well! As part of QA we need to ensure that all outbound and inbound Gateway calls use TLS 1.2, which includes: - [ ] Uptime tests - [ ] JSVM HTTP calls - [ ] Batch API - [ ] Reverse proxy - [ ] Gateway -> Dashboard communication - [ ] Gateway -> MDCB communication - [ ] UDG GraphQL and JSON data sources ## Types of changes <!-- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [x] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) - [ ] Refactoring or add test (improvements in base code or adds test coverage to functionality) ## Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply --> <!-- If you're unsure about any of these, don't hesitate to ask; we're here to help! --> - [x] Make sure you are requesting to **pull a topic/feature/bugfix branch** (right side). If pulling from your own fork, don't request your `master`! - [x] Make sure you are making a pull request against the **`master` branch** (left side). Also, you should start *your branch* off *our latest `master`*. - [x] My change requires a change to the documentation. - [ ] If you've changed APIs, describe what needs to be updated in the documentation. - [ ] If new config option added, ensure that it can be set via ENV variable - [ ] I have updated the documentation accordingly. - [x] Modules and vendor dependencies have been updated; run `go mod tidy && go mod vendor` - [ ] When updating library version must provide reason/explanation for this update. - [x] I have added tests to cover my changes. - [x] All new and existing tests passed. - [x] Check your code additions will not fail linting checks: - [x] `go fmt -s` - [x] `go vet`
Commit: | f581988 | |
---|---|---|
Author: | Josh Blakeley | |
Committer: | Matias Insaurralde |
[TT-423] Fix gRPC proxy and add h2c proxying support (#3142) Co-authored-by: gernest <geofreyernest@live.com> Co-authored-by: sredny buitrago <sredny.buitrago@gmail.com> (cherry picked from commit 4959491e55a8d4e5dd1b995d35c9a7f60c31afb3)
Commit: | 1bc2160 | |
---|---|---|
Author: | tbuchaillot |
unary
Commit: | b54b217 | |
---|---|---|
Author: | tbuchaillot |
grpc analytics
Commit: | 7d12eed | |
---|---|---|
Author: | Matias Insaurralde | |
Committer: | Matias Insaurralde |
Revert TT-423 changes (gRPC/H2C proxying). Commits: - 86a33837e8f2117208d59faa3285bdbba467c504 - 85d33f70cb01512365cf2478a1175f65f8bc1c11
Commit: | ae24e1c | |
---|---|---|
Author: | Furkan Senharputlu | |
Committer: | Matias Insaurralde |
[TT-342] Update redis to v8.3.1 (#3363) * Update redis to v8.3.1 * Remove temporary RedisOpts struct
Commit: | 1cf75bb | |
---|---|---|
Author: | Furkan Senharputlu | |
Committer: | furkansenharputlu |
[TT-342] Update redis to v8.3.1 (#3363) * Update redis to v8.3.1 * Remove temporary RedisOpts struct
Commit: | a8c3327 | |
---|---|---|
Author: | Furkan Senharputlu | |
Committer: | furkansenharputlu |
[TT-342] Update redis to v8.3.1 (#3363) * Update redis to v8.3.1 * Remove temporary RedisOpts struct
Commit: | 8d199e6 | |
---|---|---|
Author: | Furkan Senharputlu | |
Committer: | furkansenharputlu |
[TT-342] Update redis to v8.3.1 (#3363) * Update redis to v8.3.1 * Remove temporary RedisOpts struct
Commit: | f2567e9 | |
---|---|---|
Author: | Josh Blakeley | |
Committer: | Matias Insaurralde |
[TT-423] Fix gRPC proxy and add h2c proxying support (#3142) Co-authored-by: gernest <geofreyernest@live.com> Co-authored-by: sredny buitrago <sredny.buitrago@gmail.com>
Commit: | 85d33f7 | |
---|---|---|
Author: | Josh Blakeley | |
Committer: | Tyk Bot |
[TT-423] Fix gRPC proxy and add h2c proxying support (#3142) Co-authored-by: gernest <geofreyernest@live.com> Co-authored-by: sredny buitrago <sredny.buitrago@gmail.com> (cherry picked from commit 4959491e55a8d4e5dd1b995d35c9a7f60c31afb3)
Commit: | 4959491 | |
---|---|---|
Author: | Josh Blakeley | |
Committer: | GitHub |
[TT-423] Fix gRPC proxy and add h2c proxying support (#3142) Co-authored-by: gernest <geofreyernest@live.com> Co-authored-by: sredny buitrago <sredny.buitrago@gmail.com>
Commit: | 3207c82 | |
---|---|---|
Author: | Furkan Senharputlu | |
Committer: | GitHub |
[TT-342] Update redis to v8.3.1 (#3363) * Update redis to v8.3.1 * Remove temporary RedisOpts struct
Commit: | b6927da | |
---|---|---|
Author: | Furkan Senharputlu | |
Committer: | Tyk Bot |
Regenerate coprocess files for max_query_depth (#3153) Related to https://github.com/TykTechnologies/tyk/issues/3150 (cherry picked from commit ab734eb2fc22821a2b7aba1db8957559f2eb993a)
Commit: | ab734eb | |
---|---|---|
Author: | Furkan Senharputlu | |
Committer: | GitHub |
Regenerate coprocess files for max_query_depth (#3153) Related to https://github.com/TykTechnologies/tyk/issues/3150
Commit: | d436680 | |
---|---|---|
Author: | Alok G Singh | |
Committer: | Leonid Bugaev |
Fixing grpc vendor'd code (#2829) There is this commit (which is only on release-2.9) which removes some files. These missing files seem to make go get fetch the package afresh and place it $GOPATH/src which causes the build to fail. master has these files and builds fine without go gets. ``` git diff-tree -r --name-status 43865ac3 | grep balan M vendor/google.golang.org/grpc/balancer/balancer.go M vendor/google.golang.org/grpc/balancer/base/balancer.go M vendor/google.golang.org/grpc/balancer/base/base.go D vendor/google.golang.org/grpc/balancer/roundrobin/roundrobin.go M vendor/google.golang.org/grpc/balancer_conn_wrappers.go M vendor/google.golang.org/grpc/balancer_v1_wrapper.go ``` This commit adds the latest grpc (from master) as well as protobuf and genproto which were also vendor'd wrong. The two dependencies were copied over from master. This commit needs to be applied to `release-2.9` only. This should NOT go to master.
Commit: | ea166d2 | |
---|---|---|
Author: | Leonid Bugaev | |
Committer: | Leonid Bugaev |
Fix return overrides to override error bodies (#2815) The previous PR https://github.com/TykTechnologies/tyk/pull/2731 contained an error, and always forced return custom error: which brakes backward compatibility. In this PR I added tests covering all return overrides functionality and normalized its behavior for JSVM and Python. Additionally, it use reverse logic now, and plugin needs set `ReturnOverrides.OverrideError` (JS) or `return_overrides.override_error` (Python) to `true` in order to override the body of response. Additionally, I renamed `response_error` field to `response_body`, because it makes way more sense. The old field still can be set for backward compatibility. https://github.com/TykTechnologies/tyk/issues/2693
Commit: | 3fd2820 | |
---|---|---|
Author: | Leonid Bugaev | |
Committer: | GitHub |
Fix return overrides to override error bodies (#2815) The previous PR https://github.com/TykTechnologies/tyk/pull/2731 contained an error, and always forced return custom error: which brakes backward compatibility. In this PR I added tests covering all return overrides functionality and normalized its behavior for JSVM and Python. Additionally, it use reverse logic now, and plugin needs set `ReturnOverrides.OverrideError` (JS) or `return_overrides.override_error` (Python) to `true` in order to override the body of response. Additionally, I renamed `response_error` field to `response_body`, because it makes way more sense. The old field still can be set for backward compatibility. https://github.com/TykTechnologies/tyk/issues/2693
Commit: | 43865ac | |
---|---|---|
Author: | Matias Insaurralde | |
Committer: | Leonid Bugaev |
Extend ReturnOverrides (for 2.9) (#2786) Based on #2731. All gRPC and PB packages were updated, bindings generated using them.
Commit: | 42f2393 | |
---|---|---|
Author: | Matias Insaurralde | |
Committer: | Leonid Bugaev |
coprocess: make ReturnOverrides more flexible when returning errors (#2693) (#2731) For #2693, WIP so don't merge yet!
Commit: | ac8cc4b | |
---|---|---|
Author: | Geofrey Ernest | |
Committer: | Leonid Bugaev |
Update go.mod (#2405) Closes #2549
Commit: | d8457f9 | |
---|---|---|
Author: | Matias Insaurralde | |
Committer: | Leonid Bugaev |
Support response middleware when using rich plugins (#2321) Added new `response` hook type ``` { "file_list": [ ], "custom_middleware": { "pre": [ { "name": "MyPreHook" } ], "response": [{ "name": "MyResponseHook" }] } } ``` ``` from tyk.decorators import * from gateway import TykGateway as tyk @Hook def MyResponseHook(request, response, session, metadata, spec): response.raw_body = b'newbody' return response ```
Commit: | 69a6be5 | |
---|---|---|
Author: | Matias Insaurralde | |
Committer: | Leonid Bugaev |
Update http2 and grpc vendored packages (#2456) To ensure we incorporate fixes for [CVE-2019-9512](https://nvd.nist.gov/vuln/detail/CVE-2019-9512) (Ping Flood), [CVE-2019-9514](https://nvd.nist.gov/vuln/detail/CVE-2019-9514) (Reset Flood), and [CVE-2019-9515](https://nvd.nist.gov/vuln/detail/CVE-2019-9515) (Settings Flood), described [here](https://github.com/Netflix/security-bulletins/blob/master/advisories/third-party/2019-002.md). 1) `golang.org/x/net/http2` changes are [here](https://github.com/golang/net/commit/74dc4d7220e7acc4e100824340f3e66577424772). 2) `google.golang.org/grpc` was updated to the latest tag that incorporates the fixes: [v1.23.0](https://github.com/grpc/grpc-go/releases/tag/v1.23.0).
Commit: | 775ce4b | |
---|---|---|
Author: | Tyk |
Commit message
Commit: | c589132 | |
---|---|---|
Author: | Furkan Senharputlu | |
Committer: | Leonid Bugaev |
Fix gRPC and add test (#2119) Pass "Te" trailer. See https://github.com/golang/go/issues/21096 This PR adds gRPC test. Fixes https://github.com/TykTechnologies/tyk/issues/2105
Commit: | 60e903d | |
---|---|---|
Author: | Leonid Bugaev |
Revert "Fix GRPC vendoring" This reverts commit e353a703fb2c0506998cc68f31ee0f22d64b4036.
Commit: | 7172b91 | |
---|---|---|
Author: | Matias Insaurralde | |
Committer: | Leonid Bugaev |
Modify request body field (#1735) Added new byte `raw_body` `byte` field to coprocess object which filled all the time. And `body` field now filled only if its valid utf (previously just paniced)
Commit: | 0c6df69 | |
---|---|---|
Author: | Matias Insaurralde | |
Committer: | Leonid Bugaev |
coprocess: use metadata as map[string]string, enhance conversion
Commit: | 8b7d3fe | |
---|---|---|
Author: | Matias Insaurralde | |
Committer: | Leonid Bugaev |
coprocess: replace proto with URL scheme
Commit: | e353a70 | |
---|---|---|
Author: | Leonid Bugaev | |
Committer: | Leonid Bugaev |
Fix GRPC vendoring
Commit: | 1296850 | |
---|---|---|
Author: | Matias Insaurralde | |
Committer: | Leonid Bugaev |
coprocess: expose request protocol (#1702) Update bindings using "update_bindings.sh".
Commit: | cf13ebc | |
---|---|---|
Author: | Matias Insaurralde | |
Committer: | Leonid Bugaev |
Add HTTP method to middleware request object (#1386) Both JSVM and Coprocess. In addition, fixed missing "certificate" field.
Commit: | d1e10cf | |
---|---|---|
Author: | Matias Insaurralde | |
Committer: | Leonid Bugaev |
coprocess: add RequestURI
Commit: | 5984788 | |
---|---|---|
Author: | Matias Insaurralde | |
Committer: | Leonid Bugaev |
Add HTTP method to middleware request object (#1386) Both JSVM and Coprocess. In addition, fixed missing "certificate" field.
Commit: | d18d7e4 | |
---|---|---|
Author: | Daniel Martí | |
Committer: | Leonid Bugaev |
session: allow applying multiple policies And add the extra field to the proto too.
Commit: | 07956dc | |
---|---|---|
Author: | Matias Insaurralde | |
Committer: | Leonid Bugaev |
proto: add headers map for ReturnOverrides
Commit: | 98c9afa | |
---|---|---|
Author: | Matias Insaurralde | |
Committer: | Leonid Bugaev |
Extend ReturnOverrides https://github.com/TykTechnologies/tyk/pull/763
Commit: | 1ef17fc | |
---|---|---|
Author: | Matias Insaurralde | |
Committer: | Leonid Bugaev |
Extend ReturnOverrides https://github.com/TykTechnologies/tyk/pull/763
Commit: | 0381866 | |
---|---|---|
Author: | Matias Insaurralde |
Modify SessionState proto definition.
Commit: | f2e7d60 | |
---|---|---|
Author: | Matias Insaurralde |
Update SessionState.
Commit: | 8e27c44 | |
---|---|---|
Author: | Matias Insaurralde |
Update gRPC service definition to include DispatchEvent.
Commit: | 8764214 | |
---|---|---|
Author: | Matias Insaurralde |
Add gRPC service to proto definition.
Commit: | eeea392 | |
---|---|---|
Author: | Matias Insaurralde | |
Committer: | Matias Insaurralde |
Updating bindings
Commit: | 7d5d470 | |
---|---|---|
Author: | Matias Insaurralde |
Bindings update
Commit: | 93f7abc | |
---|---|---|
Author: | Matias Insaurralde |
Simplifying proto map conversion
Commit: | 61d9289 | |
---|---|---|
Author: | Matias Insaurralde |
Refactor CoProcessObject hook field name
Commit: | ebcd43c | |
---|---|---|
Author: | Matias Insaurralde |
Protobuf binding update
Commit: | d8fb9e3 | |
---|---|---|
Author: | Matias Insaurralde |
Normalizing proto definition fields
Commit: | 261808e | |
---|---|---|
Author: | Matias Insaurralde |
Moving proto definitions
Commit: | a0f1cf5 | |
---|---|---|
Author: | Matias Insaurralde |
Renaming fields to match Go structs
Commit: | f874bee | |
---|---|---|
Author: | Matias Insaurralde |
Pushing latest protocol definitions
Commit: | eebe102 | |
---|---|---|
Author: | Matias Insaurralde |
Updating nested structs
Commit: | 8cbe335 | |
---|---|---|
Author: | Matias Insaurralde |
Updating CoProcessObject proto & adding SessionState definition
Commit: | 59b93e2 | |
---|---|---|
Author: | Matias Insaurralde |
Pushing CoProcessObject proto
Commit: | 2a96953 | |
---|---|---|
Author: | Matias Insaurralde |
First protobuffer definitions