fleet/server/mdm/android
Carlo 4da1a479f9
Add Android enterprise specific ID on update (#33469)
Fixes a miss in #33368 for #33321 which causes the `host.uuid` to be empty on host updates.
2025-09-25 13:27:08 -04:00
..
mock Feature branch for Android config profiles (#32976) 2025-09-22 11:29:57 -04:00
service Add Android enterprise specific ID on update (#33469) 2025-09-25 13:27:08 -04:00
tests Feature branch for Android config profiles (#32976) 2025-09-22 11:29:57 -04:00
android.go Feature branch for Android config profiles (#32976) 2025-09-22 11:29:57 -04:00
arch_test.go Feature branch for Android config profiles (#32976) 2025-09-22 11:29:57 -04:00
datastore.go Update golangci-lint to v2.4.0 (#33251) 2025-09-22 13:17:11 -05:00
errors.go Hook up Android fleetdm.com/proxy (#29645) 2025-06-12 19:42:15 -05:00
pubsub.go Added custom auth for PubSub push endpoint. (#26664) 2025-02-27 15:16:32 -06:00
README.md Basic Android enroll functionality (#26386) 2025-02-24 14:31:21 -06:00
service.go Handle deleted Android Enterprise (#32267) 2025-09-04 08:17:37 -04:00

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.