mirror of
https://github.com/fleetdm/fleet
synced 2026-04-21 21:47:20 +00:00
bf7917b503
For #26219 Video explaining the PR: https://www.youtube.com/watch?v=t2hmpE7N-50 This PR includes: - applying a default/dummy policy to Android enterprise - Setting up PubSub topic and subscription to point at Fleet Server - Generating device enrollment token - Enrolling a device Although some tests were added, this PR is mostly manually tested. Integration tests are an outstanding task. # Checklist for submitter - [x] If database migrations are included, checked table schema to confirm autoupdate - For database migrations: - [x] Checked schema for all modified table for columns that will auto-update timestamps during migration. - [x] Confirmed that updating the timestamps is acceptable, and will not cause unwanted side effects. - [x] Ensured the correct collation is explicitly set for character columns (`COLLATE utf8mb4_unicode_ci`). - [x] Added/updated automated tests - [x] Manual QA for all new/changed functionality
879 B
879 B
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.