Skip to content

Configuration #1

Description

@ciegler

In Quarkus runtime configurations can only be changed when restarting the application and build-time configurations need an application re-augmentation.
Additionally Quarkus follows a strict order in which the application is configured.
Per default Quarkus loads configuration values form properties files only, however there are extensions for e.g. yaml.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions