Info | ||
---|---|---|
| ||
This page is a work in progress |
...
Already exists, fetching and processing the configuration JSON works just the same as any other data JSON.
Examples
Several modules already use "Distributed Configuration via Path", see these examples that show CRUD configuration APIs:
Module, type of configuration | Path |
---|---|
/inventory/config | |
/batch-voucher/export-configurations | |
/batch-voucher-storage/export-configurations | |
/orders/configuration | |
/orders-storage/configuration | |
/eventConfig | |
/converter-storage/forms/configs |
...
- Every implementation of configuration is different, meaning separate implementations and separate client code is needed.
- Each module has its own configuration interface resulting in more paperwork when comparing to the existing mod-configuration solution; the multiple interface solution and the namespace solution also require interface paperwork for each module.