Files

T

Magnus Jensen da43bf8371 Request body limits (#39080 )

<!-- Add the related story/sub-task/bug number, like Resolves #123, or
remove if NA -->
**Related issue:** Resolves
https://github.com/fleetdm/confidential/issues/13934

# Checklist for submitter

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

- [ ] 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
- [ ] QA'd all new/changed functionality manually

2026-02-05 10:29:53 -05:00

authz

…

endpointer

Request body limits (#39080 )

2026-02-05 10:29:53 -05:00

http

Request body limits (#39080 )

2026-02-05 10:29:53 -05:00

logging

Created kitlog adapter wrapping slog (#38890 )

2026-02-03 20:37:17 -06:00

middleware

…

mysql

Improved OpenTelemetry error handling (#38757 )

2026-01-26 17:07:32 -06:00

arch_test.go

Created kitlog adapter wrapping slog (#38890 )

2026-02-03 20:37:17 -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