We might want to consider implementing a D-Bus signal also here, to allow for a scenario where the client is still driving the queries, and notifies the UI when something is available.

FYI, we decided in a feature team meeting not to add any DBus endpoint for configuring intervals. See this comment for more details.

, : I'm thinking that the basic mechanism for disabling poll based update checks is to set the interval to zero in the config file. Simple and effective.

But I was also considering having a DBus endpoint for setting this value on the fly. This could be useful for example for UIs that have a setting like "check for update every X hours". The brute force approach to this is to adjust the config file, and restart the client, but this is quite nasty, and has many pitfalls (what if an update is in progress?). I'm leaning towards adding an endpoint for it, but what you think? Scope creep?

Yeah, ok, I see what you mean. It does actually change status from nothing to "pending" in a dynamic deployment. But this is ok, I think. The important thing is that it's not listed as "in progress".

The device will be set to pending at the moment you click the deploy button

this depends on the deployment type; for dynamic deployment, it's possible that at the moment you click the deploy button nothing will happen and the device will be added to the deployment (with `pending` status) when it will ask for the deployment using /deployments/next

the rest of the status transitions are done by the device, so yes, the device will not show up as `in progress`