MicroProfile Config

MicroProfile Config defines a set of supported default ConfigSources for environment variables, system properties, and META-INF/microprofile-config.properties files on the classpath with specific ordinals.

Magnolia can scan more locations for configuration properties files and uses the SmallRye Config library for implementation. It supports passing such locations through the magnolia.config.locations configuration property, which is defined as a system or environment property.

You can also specify locations via magnolia.properties.
Java system property from command line
magnolia.properties file

This enables developers to build containerized images of Magnolia once, and deploy anywhere; for example, when using Docker bind mounts or Kubernetes ConfigMaps.

Raw view of MicroProfile Config values

To see exactly where a specific MicroProfile Config property is coming from, what precedence and values it has, see the Config info tab in the About app.

To locate a property, start typing its name in the Configuration column`s filter field:

Viewing MicroProfile Config properties in the About app

Property injection

While Magnolia supports injecting @ConfigProperty fields into managed components, it’s not fully interoperable with the CDI specification.

Magnolia uses Google Guice for dependency injection.
Related topics

DX Core



This widget lets you know where you are on the docs site.

You are currently perusing through the DX Core docs.

Main doc sections

DX Core Headless PaaS Legacy Cloud Incubator modules
6.3 beta

Magnolia 6.3 beta

Magnolia 6.3 is in beta. We are updating docs based on development and feedback. Consider the 6.3 docs currently in a state of progress and not final.

We are working on some 6.3-beta known issues during this phase.