Uploaded image for project: 'Quarkus Documentation'
  1. Quarkus Documentation
  2. QDOCS-1149

[Docs] [Breaking Change]: Migration to @ConfigMapping

XMLWordPrintable

    • 3
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide
      [id="ref_rn-qdocs-1149-migration-to-configmapping_{context}"]
      = Migration to @ConfigMapping

      In {ProductLongName} {ProductVersion}, Quarkus configuration has migrated to the `@ConfigMapping` framework.
      This change replaces the previous configuration infrastructure and improves consistency across configuration sources.

      A compatibility layer remains in place for certain previously used configuration classes, but it will be removed in a future release.

      // Placeholder until confirmed content is approved
      Show
      [id="ref_rn-qdocs-1149-migration-to-configmapping_{context}"] = Migration to @ConfigMapping In {ProductLongName} {ProductVersion}, Quarkus configuration has migrated to the `@ConfigMapping` framework. This change replaces the previous configuration infrastructure and improves consistency across configuration sources. A compatibility layer remains in place for certain previously used configuration classes, but it will be removed in a future release. // Placeholder until confirmed content is approved

      Affected version: 3.19

      SME: gsmet@redhat.com 

      Resources: 

      Notes: 

      • RH supports a set of extensions whereby users can write their own extensions and use internal APIs which have never been supported. Guillaume has requested Docs to work with him to draft this update as it is a specific situation. Do not to base our RN update on the upstream migration guide. 

              mmaler@redhat.com Michal Maléř
              shjones@redhat.com Sheila Jones
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: