How can the front-end multi-project, multi-online environment and multi-region better realize the configuration scheme?

because the online environment of the company project is multiple regions, the request API at the front end and the configuration of some regions are different, so you need a unified configuration file to meet the different needs of each region. Currently, my approach is to use a json file to write the configuration of different regions, and the frontend requests the json file to read the configuration and API interface in it.
but this exposes all the configurations. I would like to ask if you have a better way to meet the needs, without having to change the configuration in different regions each time, so as to increase the pressure on the operation and maintenance team.

Profile configuration-Management nginx javascript

Aug.13,2021

the backend adds a request to get all the configurations in the current region, isn't it? Neither will all the configurations be exposed, nor will they be cut back and forth

package by region, and the configuration will be written dead in the code

Previous: The problem of inaccurate calculation of python floating point number

Next: How to dynamically assign a value to canvas to draw a rectangle according to the data coordinates of json