Files

T

Scott GressandIan Littman 30632040b1 Fix addFleetMaintainedAppEndpoint to accept fleet_id param (#41805 )

<!-- Add the related story/sub-task/bug number, like Resolves #123, or
remove if NA -->
**Related issue:** Resolves #41771

# Details

Solves two issues in 4.82:

1. The `fleet_id` param in `POST /software/fleet_maintained_apps` wasn't
being read, causing all FMAs using that param to be added to fleet ID 0
(unassigned aka No Team)
2. We were logging deprecation warnings for body params even if the
topic was turned off, meaning Fleet would generate deprecation warnings
in certain cases that users wouldn't be able to fix.

# 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
Added unit tests for the decoder since it's got one-off logic in it
- [X] QA'd all new/changed functionality manually
  - [X] Added an FMA to a fleet successfully using `fleet_id`
- [X] Added an FMA to a fleet successfully using `team_id` and saw
deprecation warning
  - [X] Added an FMA to "Unassigned" successfully using `fleet_id=0`
  - [X] Added an FMA to "Unassigned" successfully using `team_id=0`
- [X] Added an FMA to "Unassigned" successfully with no `fleet_id` or
`team_id` param (this seems like a bug but it's existing behavior)

---------

Co-authored-by: Ian Littman <iansltx@gmail.com>

2026-03-17 09:59:03 -05:00

authz

…

endpointer

Fix addFleetMaintainedAppEndpoint to accept fleet_id param (#41805 )

2026-03-17 09:59:03 -05:00

errors

Move PostJSONWithTimeout to platform/http package and activity cleanup (#40561 )

2026-02-26 17:39:10 -06:00

http

Fix data race in ErrorWithUUID.UUID() causing CI test failures (#40961 )

2026-03-05 09:17:51 -06:00

logging

Final slog migration PR: test infrastructure + tools + remaining standalone files (#40727 )

2026-02-28 05:52:21 -06:00

middleware

Added per-IP rate limiting and response caching (#41516 )

2026-03-13 15:21:16 -05:00

mysql

slog migration: initLogger + serve.go + cron + schedule (#40699 )

2026-02-27 14:29:27 -06:00

arch_test.go

Move PostJSONWithTimeout to platform/http package and activity cleanup (#40561 )

2026-02-26 17:39:10 -06:00

README.md

…

README.md

Platform packages

This directory contains infrastructure and cross-cutting technical concerns that are independent of Fleet's business domain. These packages provide foundational capabilities used across the codebase.

Platform vs domain

Following separation of concerns, we distinguish:

Platform (infrastructure): Technical concerns like database connectivity, HTTP utilities, middleware, and transport-level error handling. These packages have no knowledge of Fleet's business domain.
Domain (business logic): Feature-specific code organized into bounded contexts. Domain packages depend on platform packages, not the reverse.

Guidelines

Platform packages must not import domain packages
Platform packages should be general-purpose and reusable
Architectural boundaries are enforced by arch_test.go