fleet/server/service/contract
Lucas Manuel Rodriguez 33a15831c0
Add missing platform_like during orbit enrollment (#32671)
#30877

We need to send `platform_like` during orbit enrollment for proper setup
experience for Linux

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))
- [ ] 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))
2025-09-05 16:05:19 -03:00
..
orbit.go Add missing platform_like during orbit enrollment (#32671) 2025-09-05 16:05:19 -03:00
osquery.go Fleet server verifies HTTP signature (#30825) 2025-07-16 20:08:27 +02:00
README.md Added scim/details endpoint (#28007) 2025-04-10 14:08:45 -05:00
scim.go Added scim/details endpoint (#28007) 2025-04-10 14:08:45 -05:00
sessions.go Added scim/details endpoint (#28007) 2025-04-10 14:08:45 -05:00

📦 contract Package

This package contains the request and response structs used by the HTTP API.

Keeping these in a separate package makes the code:

  • Easier to maintain — the shape of API data is defined in one place
  • Clearer — shows exactly what the API expects and returns
  • Reusable — the same types can be used by handlers, tests, or clients

This package should only define data structures — no business logic.

🔄 Note: Some request/response structs may still live in the server/service packages. Move them here as needed to keep API contracts organized and consistent.