Azure / Azure/dotnet-template-azure-iot-edge-module
No separate ModuleClient instance per Background Service
- Dominant language
- C#
- Stars
- 16
- Forks
- 28
- PR merge metrics
- No merged PRs in 30d
Description
The new IoT Edge module template generates code for using background-services. However, a new ModuleClient instance is instantiated per BackgroundService, which is imo not a best practice.
Ideally, you should have one ModuleClient instance per iotedge module.
See also my remark [here](https://github.com/microsoft/vs-azure-iot-edge-docs/issues/42#issuecomment-1406804810).
Contributor guide
Research direction
The issue names no files or tests; start by locating the IoT Edge module template code that generates background services and creates ModuleClient instances. Check how the generated module shares client state across services. Done means generated code creates one ModuleClient per IoT Edge module rather than one per BackgroundService, with relevant generation tests updated if present.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, csharp
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100