Files

T

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

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

This is preparatory work before incrementally converting datastore/mysql
files to directly use *slog.Logger.
This will be done by using `logger.SlogLogger()` to get the underlying
`*slog.Logger`

# Checklist for submitter

- [ ] Changes file added for user-visible changes in `changes/`,
`orbit/changes/` or `ee/fleetd-chrome/changes`.
  - Changes file already exists from 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**
* Updated internal logging infrastructure to use a standardized platform
logging package across database and utility components. This
consolidates logging dependencies and improves system consistency
without affecting user-facing functionality.

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

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

authz

Activity bounded context: Complete read operations (#38555 )

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

endpointer

Correct err check endpoint (#39559 )

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

http

Correct err check endpoint (#39559 )

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

logging

Changes needed before gokit/log to slog transition. (#39527 )

2026-02-11 10:08:33 -06:00

middleware

…

mysql

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

2026-02-17 15:29:52 -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