This issue is to track the design and documentation of the V2 Agent API
I'm not sure if this is required for the initial V2 release, at some point I would like to have a UI for the agent that allows troubleshooting by viewing logs and also GUI configuration, and then this will be required, but perhaps this will not happen in V2.0 maybe this can be deferred to a later release?
We may need to design the API now as part of the initial agent and just provide the UI later, or maybe we can defer a major re-write of the agent to a later release and limit the agent changes in the V2.0 release to just being a consumer of the new Manager API's.
Lots to think about
The goal is fro the V2 Agent API to be to a real REST API (not there was never a V1 API)
The V2 API needs to:
- provide API endpoints to read/update settings
- provide API endpoints to read data for display
This issue is to track the design and documentation of the V2 Agent API
I'm not sure if this is required for the initial V2 release, at some point I would like to have a UI for the agent that allows troubleshooting by viewing logs and also GUI configuration, and then this will be required, but perhaps this will not happen in V2.0 maybe this can be deferred to a later release?
We may need to design the API now as part of the initial agent and just provide the UI later, or maybe we can defer a major re-write of the agent to a later release and limit the agent changes in the V2.0 release to just being a consumer of the new Manager API's.
Lots to think about
The goal is fro the V2 Agent API to be to a real REST API (not there was never a V1 API)
The V2 API needs to: