api-testing/extensions
Rick 05c338ea35
feat: support to get pprof of an extension (#307)
Co-authored-by: rick <LinuxSuRen@users.noreply.github.com>
2023-12-07 11:06:45 +08:00
..
collector feat: support to show the error count as summary in report (#305) 2023-12-05 13:59:16 +08:00
monitor-docker feat: support to show the error count as summary in report (#305) 2023-12-05 13:59:16 +08:00
store-etcd feat: support to get pprof of an extension (#307) 2023-12-07 11:06:45 +08:00
store-git feat: support to get pprof of an extension (#307) 2023-12-07 11:06:45 +08:00
store-mongodb feat: support to get pprof of an extension (#307) 2023-12-07 11:06:45 +08:00
store-orm feat: support to get pprof of an extension (#307) 2023-12-07 11:06:45 +08:00
store-s3 feat: support to get pprof of an extension (#307) 2023-12-07 11:06:45 +08:00
README.md feat: add a new extension: mongodb (#278) 2023-11-18 13:58:34 +08:00

README.md

Ports in extensions:

Name Port
orm 4071
s3 4072
etcd 4073
git 4074
mongodb 4075

Contribute a new extension

  • First, create a directory in current directory. And please keep the same naming convertion.
  • Second, implement the Loader gRPC service which defined by this proto.
  • Finally, add the extension's name into function SupportedExtensions.

Naming conventions

Please follow the following conventions if you want to add a new store extension:

store-xxx

xxx should be a type of a backend storage.

Test

First, build and copy the binary file into the system path. You can run the following command in the root directory of this project:

make build-ext-etcd copy-ext