Victor Lyuboslavsky
67d0c576b1
<!-- Add the related story/sub-task/bug number, like Resolves #123, or remove if NA --> **Related issue:** Resolves #42600 Unreleased bug: https://github.com/fleetdm/fleet/issues/42600#issuecomment-4220428519 # Checklist for submitter ## Testing - [x] Added/updated automated tests - [x] QA'd all new/changed functionality manually For unreleased bug fixes in a release candidate, one of: - [x] Confirmed that the fix is not expected to adversely impact load test results <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Bug Fixes** * Re-enrolling devices now fully reset certificate templates: templates return to pending (install retained), retry counts and delivery metadata are cleared to avoid stale state. * **Behavior** * Re-enrollment explicitly deletes prior device certificate entries before creating fresh pending templates to prevent duplicates and stale data. * **Tests** * Added tests covering Android re-enrollment to verify templates are recreated and metadata is cleared. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
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.