Files

T

Scott Gress 772fb12cf5 Add more deprecation logs and mute by default (#40305 )

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

# Details

* Adds deprecation warnings to `fleetctl apply`
* Adds alias conflict errors (i.e. using both new and deprecated keys in
the same spec) to `fleetctl apply`
* Adds logic around all deprecated field warnings to check the topic
first
* Disables deprecation warnings by default for `fleet serve`, `fleetctl
gitops` and `fleetctl apply`
* Enables deprecation warnings for dogfood via env var

To turn on warnings:
* In `fleet serve`, use either
`--logging_enable_topics=deprecated-field-names` or the
`FLEET_LOGGING_ENABLE_TOPICS=deprecated-field-names` env var
* In `fleetctl gitops` / `fleetctl apply` use either
`--enable-log-topics=deprecated-field-names` or
`FLEET_ENABLE_LOG_TOPICS=deprecated-field-names`

# Checklist for submitter

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

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

tested in `fleetctl apply`, `fleet serve` and `fleet gitops` that
warnings are suppressed by default and added when the appropriate env
var or CLI option is used

2026-02-23 23:09:08 -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

Order By Vulnerability (#40143 )

2026-02-23 09:42:36 -07:00

arch_test.go

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

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