You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 21, 2024. It is now read-only.
It was not really solved. I meant that for example there is a firewall, which has a public endpoint with host/ip/mac info, and we can consume this endpoint at app start.
So the current flow is:
the app starts
read the config
read the file to memory based on the config
work based on that file
The new flow would be:
the app starts
reads the config
decide if we do the old file reading or the new api reading thing
if we do the api reading thing somehow consume the remote endpoint, parse the data
work based on that data
One of the biggest question is probably the "what kind of response data we can consume", I would go with a simple csv like format first (like the current file), and maybe a fixed json based too. (probably the format can come from config too)
Add an option to read the name/ip/mac list from a rest endpoint (by get with a configurable url).
The text was updated successfully, but these errors were encountered: