Split `create_device` endpoint in enrollment service into more granular endpoints
Open
optional for release
refactoring
- Dominant language
- Rust
- Stars
- 2.8k
- Forks
- 115
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 51
Description
`create_device` is currently used to serve at least three functions:
- actually creating user devices during enrollment
- registering network devices
- activating desktop clients
This results in a method that's ~400 lines long and trending towards being unmaintainable.
We should split it into dedicated endpoint for each of those functionalities.
Contributor guide
Assessment
This issue has not been assessed yet.