api-testing/e2e
Rick e866727d53
feat: support to run test suite via http (#478)
* feat: support to run test suite via http

* improve the extension download

* download extenion in the e2e

* add extension-registry into the helm values.yaml file

* update helm install in e2e test

* fix the k8s helm chart testing

---------

Co-authored-by: rick <linuxsuren@users.noreply.github.com>
2024-06-10 18:52:33 +08:00
..
code-generator fix: python generated code error when without HTTP headers (#465) 2024-06-01 22:09:36 +08:00
Dockerfile test: add k8s e2e test (#270) 2023-11-13 14:24:21 +08:00
README.md fix: not work when grpc port is a random one (#467) 2024-05-31 13:40:57 +08:00
compose-external.yaml feat: add graphql feature support (#326) 2023-12-21 11:15:12 +08:00
compose-k8s.yaml feat: support to run test suite via http (#478) 2024-06-10 18:52:33 +08:00
compose.yaml test: add unit test cases for github reporting (#299) 2023-11-30 18:11:25 +08:00
entrypoint.sh feat: support to run test suite via http (#478) 2024-06-10 18:52:33 +08:00
git.yaml chore: move the system serivce into linuxsuren/go-service (#328) 2023-12-25 14:49:53 +08:00
k8s.sh feat: support to run test suite via http (#478) 2024-06-10 18:52:33 +08:00
openssl.cnf feat: add TLS for gRPC server endpoint (#477) 2024-06-09 17:42:01 +08:00
start.sh feat: support to run test suite via http (#478) 2024-06-10 18:52:33 +08:00
test-suite-common.yaml feat: support to run test suite via http (#478) 2024-06-10 18:52:33 +08:00

README.md

You can build the image locally in the repository root directory:

If you are a Linux/MacOS user, you can use the following command:

REGISTRY=ghcr.io TAG=master make image

If you are a Windows user, you can use the following command:

Set-Content -Path "env:REGISTRY" -Value "ghcr.io"
Set-Content -Path "env:TAG" -Value "master"
make image