liveBook · Manning

Configuration editor

As explained in Quarkus in Action

A configuration editor is an interface for viewing and modifying an application's configuration settings.

A configuration editor is the Config Editor panel in Quarkus Dev UI. It displays configuration properties understood by Quarkus and the extensions used by the application, including properties without explicitly assigned values. section 3.3.1

Use the editor to inspect and change application configuration:

  • Review built-in quarkus.* properties, application-specific properties, JVM system properties, and environment variables. section 3.3.1
  • See default values for properties that have not been configured. section 3.3.1
  • Edit writable values; changes persist to application.properties, or add new entries there when a property was previously absent. section 3.3.1
  • Treat edits to displayed system properties and environment variables carefully: adding the same name to application.properties does not change values returned by System.getProperties() or System.getenv(). section 3.3.1

How Quarkus in Action covers it

How deep it goes
Lists defaults and writable properties, then stops short of making application.properties values system properties or environment variables.
Examples
Uses a long property table, default values, edited entries, and newly added application.properties settings as concrete examples.
What it assumes
Assumes a Quarkus application with Dev UI and configuration properties supplied by Quarkus, extensions, or application code.
What you can do after
Operate/configure Quarkus settings from Dev UI and persist edits to application.properties.
How it connects
Connects Quarkus Dev UI with extensions, application.properties, YAML configuration, JVM system properties, environment variables, and MicroProfile Config.

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.