In fixing the errors in retrieve operations in T5006, async was unnecessarily added to configure operations as well; this introduces a bug when a configure operation wants to itself make a call to the http-api. Though not common, perhaps, this is reasonable and supported, except for the bug introduced by overreach in addressing T5006.

The details: the web framework being used, FastAPI/Starlette handles non-async vs async functions by adding the former to a thread pool, which is itself awaited for execution; functions defined as async are run within an event-loop. For non-native async functions, defining them as async will introduce blocking within the event-loop: this is appropriate for retrieve operations that have no internal locking; undesirable for configure operations which do have locking and should not block.