fleet/server/mdm/android
2025-08-25 11:41:28 -04:00
..
mock Merge Android datastore into main Fleet datastore (#32233) 2025-08-25 11:41:28 -04:00
service Merge Android datastore into main Fleet datastore (#32233) 2025-08-25 11:41:28 -04:00
tests Merge Android datastore into main Fleet datastore (#32233) 2025-08-25 11:41:28 -04:00
android.go Added Android activity and better handling of deleted users. (#26640) 2025-02-27 14:19:15 -06:00
arch_test.go Merge Android datastore into main Fleet datastore (#32233) 2025-08-25 11:41:28 -04:00
datastore.go Auto-generate and check Android schema.sql (#26720) 2025-02-28 16:30:40 -06: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 IdP Authentication before BYOD (#32017) 2025-08-18 18:31:53 +02: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.