mirror of
https://github.com/fleetdm/fleet
synced 2026-05-18 22:49:19 +00:00
ebfacd3f36
<!-- Add the related story/sub-task/bug number, like Resolves #123, or remove if NA --> **Related issue:** Resolves #33060 # Checklist for submitter If some of the following don't apply, delete the relevant line. ## Testing For unreleased bug fixes in a release candidate, one of: - [x] Confirmed that the fix is not expected to adversely impact load test results |
||
|---|---|---|
| .. | ||
| mock | ||
| service | ||
| tests | ||
| android.go | ||
| arch_test.go | ||
| datastore.go | ||
| errors.go | ||
| pubsub.go | ||
| README.md | ||
| service.go | ||
The MDM Android package attempts to decouple Android-specific service and datastore implementations from the core Fleet server code.
Any tightly coupled code that needs both the core Fleet server and the Android-specific features must live in the main server/fleet, server/service, and server/datastore packages. Typical example are MySQL queries. Any code that implements Android-specific functionality should live in the server/mdm/android package. For example, the common code from server/datastore package can call the android datastore methods as needed.
This decoupled approach attempts to achieve the following goals:
- Easier to understand and find Android-specific code.
- Easier to fix Android-specific bugs and add new features.
- Easier to maintain Android-specific feature branches.
- Faster Android-specific tests, including ability to run all tests in parallel.