What a build contains
What a build of an application with spring_boot_starter_actuator contains, and when something is not in it. A module that follows a key reads it when build_runner runs, from application.yml or application.properties without a profile (see Modules left out of the build). The modules of the packages it depends on come with it: for spring_boot_dart, see Auto-configuration.
By key
build: AutoConfigurationBuild(key): true puts the module in every build, false leaves it out with all its code, and when the key is not set the Not set column decides.
| Module | Key | Not set | What it holds |
|---|---|---|---|
springBootStarterActuatorQpsAutoConfiguration |
spring.web.debug.qps.enabled |
no build | The qps endpoint of the web starter's debug feature qps; so without the feature the application has neither the counting nor the endpoint. Also native only. |
By platform
platform:: the module is only in the build of that platform; no property is read.
| Module | Platform | What it holds |
|---|---|---|
springBootStarterActuatorAutoConfiguration |
native |
The health, info and mappings endpoints, their contributors and their answers over the web starter, after the web starter's module. |
native: builds where dart:io exists (a server, an AOT executable, a Flutter app on a phone or a desktop), not a browser build. server: native without Flutter, never a Flutter app. -DSPRING_ALL_PLATFORMS=true keeps every module.
What the generator writes for it
A part of the generator (see Starter parts) runs only when the application reaches its package.
| Part or builder | What it does |
|---|---|
Actuator part (spring_boot_actuator) |
Adds build-info.properties (the name and version of the pubspec.yaml, which the info endpoint shows) to the resources of an application (publish_to: none); a lib/resources/build-info.properties of the app wins. |
| Through its dependencies | The web part, since the packages depend on spring_web_dart. |
Good to know
- A browser build has none of the starter's modules.