api-testing/extensions
Rick 1372e6d21d
feat: support to show databases and tables on ui (#631)
* feat: support to show databases and tables

* support to show database and tables

* support to show databases and tables

* feat: add urlEncode and urlDecode functions to template rendering

* fix: update copyright year and add password placeholder handling in store update

* feat(DataManager): add support for multiple databases

- Add currentDatabase parameter to DataQuery function
- Update API request to include X-Database header
- Modify query object for atest-store-orm to include database key

* feat(console): enhance database manager functionality and layout

- Add queryDataFromTable and queryTables functions
- Implement database and table selection
- Adjust layout for better usability
- Optimize SQL query execution

* fix the scrollbar issues on the data manager page

* add etcd and orm compitable

* add redis key-value query support

* support to let user to choose store param from list

* update readme file

* fix the frontend unit test issues

---------

Co-authored-by: rick <linuxsuren@users.noreply.github.com>
2025-03-02 16:38:13 +08:00
..
README.md feat: support to show databases and tables on ui (#631) 2025-03-02 16:38:13 +08:00

README.md

Ports in extensions:

Type Name Port
Store orm 4071
Store s3 4072
Store etcd 4073
Store git 4074
Store mongodb 4075
Store redis
Monitor docker-monitor
Agent collector
Secret Vault

Contribute a new extension

  • First, create a repository. 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