Is your feature request related to a problem? Please describe.
Infrared does currently have a simple REST-API but it's missing 2 core features: listing all currently active configs as well as retreiving a sample config.
Describe the solution you'd like
Implement 2 new API routes, preferably GET /proxies for retreiving all currently active proxies and GET /proxies/{fileName} for retreiving the contents of a specific config file.
Describe alternatives you've considered
I have made my way around this issue by simply reading the contents of the config directory and parsing all contents of these files into one bis JSON array. But there are wayyy more points of failure in this rather than doing this by the built-in REST API.
Is your feature request related to a problem? Please describe.
Infrared does currently have a simple REST-API but it's missing 2 core features: listing all currently active configs as well as retreiving a sample config.
Describe the solution you'd like
Implement 2 new API routes, preferably
GET /proxiesfor retreiving all currently active proxies andGET /proxies/{fileName}for retreiving the contents of a specific config file.Describe alternatives you've considered
I have made my way around this issue by simply reading the contents of the config directory and parsing all contents of these files into one bis JSON array. But there are wayyy more points of failure in this rather than doing this by the built-in REST API.