Files

T

Victor Lyuboslavsky 8c2ad7f901 Run multiple independent Fleet dev servers in parallel (#41865 )

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

Docs updates: https://github.com/fleetdm/fleet/pull/41868/changes

# Checklist for submitter

- changes not needed since this is a dev environment and test issue

## Testing

- [x] QA'd all new/changed functionality manually

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

* **Tests**
* Enhanced test infrastructure to support environment-variable-based
configuration for SAML, mail, database, and S3 services, enabling more
flexible and dynamic test setups.

* **Chores**
* Updated Docker Compose configuration to use environment variables for
service ports, allowing runtime customization while maintaining backward
compatibility with default values.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->

2026-03-18 13:58:58 -05:00

authz

Activity bounded context: Complete read operations (#38555 )

2026-02-09 15:29:12 -06:00

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

Run multiple independent Fleet dev servers in parallel (#41865 )

2026-03-18 13:58: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