Files

T

Victor Lyuboslavsky ccc36a9cb3 Finishing mysql package migration to slog (#40350 )

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

# Checklist for submitter

- [ ] Changes file added for user-visible changes in `changes/`,
`orbit/changes/` or `ee/fleetd-chrome/changes`.
  - Already present in previous PR

## Testing

- [x] Added/updated automated tests
- [x] QA'd all new/changed functionality manually


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

* **Chores**
* Migrated logging to a structured, context-aware backend for clearer,
richer diagnostics and consistent log formatting.
* Introduced broader context propagation and adjusted internal
interfaces to support the new logging approach (no end-user behavior
changes).
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

2026-02-24 16:52:36 -06:00

authz

Activity bounded context: Complete read operations (#38555 )

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

endpointer

Add more deprecation logs and mute by default (#40305 )

2026-02-23 23:09:08 -06:00

http

Correct err check endpoint (#39559 )

2026-02-10 09:23:27 -05:00

logging

Add more deprecation logs and mute by default (#40305 )

2026-02-23 23:09:08 -06:00

middleware

Fixed client-side errors being incorrectly reported as server errors in OTEL telemetry (#40051 )

2026-02-19 16:06:00 -06:00

mysql

Finishing mysql package migration to slog (#40350 )

2026-02-24 16:52:36 -06:00

arch_test.go

Change Datastore.logger type to *logging.Logger (#39938 )

2026-02-17 15:29:52 -06:00

README.md

Moved common_mysql package to server/platform/mysql (#38017 )

2026-01-08 13:17:19 -06:00

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