Files

T

Victor Lyuboslavsky 36ad83f611 Android Wi-Fi profile withheld until cert installed on device (#42877 )

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

Demo video: https://www.youtube.com/watch?v=F3nfFvwdj-c

# 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`.

## 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

* **New Features**
* Android Wi‑Fi configuration profiles that reference client
certificates are withheld until the certificate is installed or reaches
a terminal state.
* Host OS settings now show the specific pending reason in the detail
column when Android profiles are waiting on certificate installation.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

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

authz

…

endpointer

ACME MDM -> main (#42926 )

2026-04-02 15:56:31 -05:00

errors

…

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

…

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