- 06 Nov, 2021 2 commits
-
-
Mark Tyneway authored
go/proxyd: Collect special errors in a dedicated metric, pass content-type header
-
Matthew Slipper authored
-
- 05 Nov, 2021 4 commits
-
-
Matthew Slipper authored
go/proxyd: ENG-1596 support authenticated client requests
-
Matthew Slipper authored
-
Mark Tyneway authored
go/proxyd: rate limiting and WS support
-
Matthew Slipper authored
-
- 04 Nov, 2021 2 commits
-
-
Ben Wilson authored
Update proxyd github actions
-
Ben Wilson authored
Update canary to build proxyd and rpc-proxy fixed "runs-on" value fixing env step Update docker build context Added env back to action
-
- 02 Nov, 2021 8 commits
-
-
Mark Tyneway authored
Add proxy method metrics
-
Matthew Slipper authored
-
Matthew Slipper authored
-
Mark Tyneway authored
Version Packages
-
github-actions[bot] authored
-
Mark Tyneway authored
Develop -> Master PR
-
Mark Tyneway authored
ci: trigger releases
-
Mark Tyneway authored
-
- 01 Nov, 2021 9 commits
-
-
Mark Tyneway authored
Develop -> Master Release PR
-
Mark Tyneway authored
Version Packages
-
github-actions[bot] authored
-
Mark Tyneway authored
Develop -> Master PR
-
Mark Tyneway authored
fix: ci publish proxy
-
Mark Tyneway authored
For rpc-proxy and proxyd. Just a patch changeset to trigger releases as a bug prevented releases previously.
-
Mark Tyneway authored
The variables used in the canary release were used in the actual release, causing it to not have the correct variables in place. This caused the CI to skip the steps for publishing the `rpc-proxy` and `proxyd`. This commit should fix the problem.
-
Matthew Slipper authored
-
Matthew Slipper authored
-
- 30 Oct, 2021 5 commits
-
-
Mark Tyneway authored
Develop -> Master Release PR
-
Mark Tyneway authored
Version Packages
-
github-actions[bot] authored
-
Mark Tyneway authored
Develop -> Master
-
Mark Tyneway authored
Add CORS support to the proxy
-
- 29 Oct, 2021 10 commits
-
-
Matthew Slipper authored
-
Mark Tyneway authored
workflows: fix build-args syntax
-
Mark Tyneway authored
The docs specify that `build-args` for the Github action `docker/build-push-action@v2` should be a list, but doing so results in an error: `The workflow is not valid. .github/workflows/release.yml (Line: 362, Col: 13): A sequence was not expected` This updates the syntax to copy the example here: https://github.com/docker/build-push-action/blob/3c507bedc4de3249e107413a7358ae1af558fd79/UPGRADE.md#L68 Uncertain if the env var parsing will work with this syntax
-
Mark Tyneway authored
Develop -> Master PR
-
Mark Tyneway authored
Bypass lua checking when the request is not a POST
-
Ben Wilson authored
-
Matthew Slipper authored
-
Ben Wilson authored
Fixed nit, added changeset for rpc-proxy
-
Mark Tyneway authored
Add proxy RPC daemon
-
Matthew Slipper authored
-