Elgato_dark/fleet
1
0
Fork 0
mirror of https://github.com/fleetdm/fleet synced 2026-05-06 06:48:54 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 117
fleet/docs/Contributing/product-groups
History
Magnus Jensen a187842260
always send webhook while device is unmanaged for MDM migration (#39416) 
<!-- Add the related story/sub-task/bug number, like Resolves #123, or
remove if NA -->
**Related issue:** Resolves #38322 

This PR utilizes the ping/status ticker that sees if the device is
Unmanaged (aka. not enrolled from a Fleet server perspective), if the
Migrate to Fleet flow before had set the `mdm_migration.txt` file, but
somehow not successfully unenrolled the device, we now keep sending it
if you trigger the modal again.

We wait 90seconds after start, so at most the user can go through the
flow every 90s, but the server has a hard limit on at most one webhook
every 3m, but still it means the user can wait a bit and retry and still
see the webhook gets sent now.

_PS: Updated the old migration test to go from 1,5m to ~2s execution
time with parallel and configurable waitForUnenrollment time (to allow
test to set lower values)

# Checklist for submitter

If some of the following don't apply, delete the relevant line.

- [x] Changes file added for user-visible changes in `changes/`,
`orbit/changes/` or `ee/fleetd-chrome/changes`.
See [Changes
files](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/guides/committing-changes.md#changes-files)
for more information.


## Testing

- [x] Added/updated automated tests
- [x] QA'd all new/changed functionality manually

## fleetd/orbit/Fleet Desktop

- [x] Verified compatibility with the latest released version of Fleet
(see [Must
rule](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/workflows/fleetd-development-and-release-strategy.md))
- [x] If the change applies to only one platform, confirmed that
`runtime.GOOS` is used as needed to isolate changes
- [x] Verified that fleetd runs on macOS, Linux and Windows
- [x] Verified auto-update works from the released version of component
to the new version (see [tools/tuf/test](../tools/tuf/test/README.md))

---------

Co-authored-by: Jordan Montgomery <elijah.jordan.montgomery@gmail.com>
2026-02-09 14:08:54 -05:00
..
mdm always send webhook while device is unmanaged for MDM migration (#39416) 2026-02-09 14:08:54 -05:00
orchestration False negative vulnerability for Adobe Acrobat Reader DC (#39131) 2026-02-05 07:20:16 -04:00
security-compliance Moving Android certificates docs. (#37622) 2026-01-09 09:27:44 -06:00
software Organize contributor docs and establish ADR process and template (#29101) 2025-05-17 15:03:52 -05:00
README.md Organize contributor docs and establish ADR process and template (#29101) 2025-05-17 15:03:52 -05:00

README.md

Fleet product groups

Fleet is organized into three main product groups:

MDM

The MDM product group focuses on Mobile Device Management, including:

  • Apple MDM (macOS, iOS)
  • Windows MDM
  • Android MDM
  • End user authentication
  • Disk encryption
  • Automated device enrollment

Orchestration

The Orchestration product group focuses on device orchestration using osquery, including:

  • Live queries
  • Scheduled queries
  • Query packs
  • Host vitals
  • Teams and access control
  • File carving
  • Policies
  • Scripts

Software

The Software product group focuses on software management, including:

  • Software inventory
  • Vulnerability management
  • Software installation
  • Software updates
  • Software policies
  • Fleet-maintained apps

Cross-Product Documentation

Some documentation applies to multiple product groups: