liveBook · Manning

Microprofile config api

As explained in Quarkus in Action

MicroProfile Config is a MicroProfile specification for supplying and accessing application configuration values from external and contextual sources.

Use the MicroProfile Config API when application code must access configuration values supplied through application.properties, YAML configuration, system properties, or environment variables. These sources are not automatically exposed as Java system properties or environment variables. section 3.3.1

In Quarkus development, Dev UI can change configuration, persist the change in application.properties, and trigger an automatic reload. This makes configuration behavior visible while developing, but persisted entries may need manual removal. section 3.3.1

Changing a Quarkus logging property

Set quarkus.log.console.darken to 1 in Dev UI. Quarkus writes the property to application.properties, reloads the application, and displays subsequent terminal log messages darker; changing it back to 0 does not remove the property automatically. section 3.3.1

How Quarkus in Action covers it

How deep it goes
Distinguishes configuration storage from application access and demonstrates Dev UI updates, but does not show API code.
Examples
Demonstrates changing quarkus.log.console.darken through Dev UI and observing persistence, reload, and darker terminal logs.
What it assumes
Assumes familiarity with application.properties or YAML, system properties, environment variables, and basic Quarkus development.
What you can do after
Apply via the MicroProfile Config API when application code needs configuration values from external or contextual sources.
How it connects
Connects application.properties, YAML configuration, system properties, environment variables, Quarkus, and Dev UI.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Quarkus in Action. The section links point to the parts of the book it draws on.