11ab39f11f
* feat: support to download differnt kinds of ext
* support to load swaggers from an extension
* docs(extension): add swagger data extension and update documentation
- Add swagger data extension to the extensions list
- Update documentation to include new extension usage
* Potential fix for code scanning alert no. 69: Arbitrary file access during archive extraction ("Zip Slip")
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Signed-off-by: Rick <1450685+LinuxSuRen@users.noreply.github.com>
---------
Signed-off-by: Rick <1450685+LinuxSuRen@users.noreply.github.com>
Co-authored-by: rick <LinuxSuRen@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
|
||
|---|---|---|
| .. | ||
| README.md | ||
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 | |
| Data | Swagger |
Contribute a new extension
- First, create a repository. And please keep the same naming convertion.
- Second, implement the
LoadergRPC 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