Files

T

Juan Fernandez 2b35eabd5d Added middleware for api-only users auth (#43772 )

Fixes #42885

Added new middleware (APIOnlyEndpointCheck) that enforces 403 for
API-only users whose request either isn't in the API endpoint catalog or
falls outside their configured per-user endpoint restrictions.

2026-04-21 07:11:33 -04:00

authz

…

endpointer

Added middleware for api-only users auth (#43772 )

2026-04-21 07:11:33 -04:00

errors

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

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

http

Use http.MaxBytesReader on the raw body and on the gzip decode output (#42265 )

2026-03-25 06:27:58 -03:00

logging

Android Wi-Fi profile withheld until cert installed on device (#42877 )

2026-04-07 16:26:09 -05:00

middleware

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

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

mysql

Added OTEL DB stats metrics, renamed trace attributes to expected OTEL names (#42097 )

2026-03-20 11:07:58 -05: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