github-such-software/adaptive-multi-protocol-gateway
1
0
Fork 0
mirror of https://github.com/Such-Software/adaptive-multi-protocol-gateway.git synced 2026-10-17 15:41:41 +02:00
Code Issues Packages Projects Releases Wiki Activity

Add route catalog manifest generator

Browse Source
This commit is contained in:
jwinterm
2026-07-06 04:16:09 -04:00
parent 407d4d106a
commit 38d86adfbf
7 changed files with 200 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/configuration.md
+5
View File
@@ -207,9 +207,14 @@ The public schema is committed at `schemas/ampg.route-manifest.v1.schema.json`.
Applications can validate generated manifests before AMPG config parsing:
```sh
python3 tools/generate_route_manifest.py examples/route-catalog.json examples/route-manifest.json
python3 -m ampg route-manifest validate routes.json
```
`examples/route-catalog.json` is a neutral app-side input shape. Real framework adapters
can replace it with generated route data from the application's router, then emit the same
AMPG route-manifest contract.
```json
{
"schema": "ampg.route-manifest.v1",
docs/interactive-apps.md
+4
View File
@@ -59,9 +59,13 @@ The schema is generated at `schemas/ampg.route-manifest.v1.schema.json`, and app
validate generated manifests with:
```sh
python3 tools/generate_route_manifest.py examples/route-catalog.json examples/route-manifest.json
python3 -m ampg route-manifest validate routes.json
```
`examples/route-catalog.json` shows the adapter side of the workflow: app route metadata
goes in, the stable AMPG route manifest comes out.
Required top-level fields:
- `schema`: must be `ampg.route-manifest.v1`.