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

[Breaking Change]: .enable → .enabled in configuration properties

XMLWordPrintable

    • 3
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide
      :_mod-docs-content-type: REFERENCE
      [id="ref_rn-qdocs-1331-enable-to-enabled-in-configuration-properties"]
      = Configuration: Use `.enabled` instead of `.enable` in configuration properties

      In the current release, feature toggles in configuration use the `.enabled` suffix instead of `.enable`.
      This change enhances consistency across configuration properties and prevents the mixing of suffixes.
      The old `.enable` properties remain recognized for backward compatibility but are deprecated.

      Run `quarkus update` to automatically migrate your configuration.
      If you update manually, rename keys such as `quarkus.log.console.enable` to `quarkus.log.console.enabled` to avoid deprecation warnings.
      Named logging handlers follow the same rule and use `quarkus.log.handler.*."handler-name".enabled`.

      Impacted properties include:

      * `quarkus.keycloak.policy-enforcer.enable` → `quarkus.keycloak.policy-enforcer.enabled`
      * `quarkus.log.console.enable` → `quarkus.log.console.enabled`
      * `quarkus.log.console.async.enable` → `quarkus.log.console.async.enabled`
      * `quarkus.log.file.enable` → `quarkus.log.file.enabled`
      * `quarkus.log.file.async.enable` → `quarkus.log.file.async.enabled`
      * `quarkus.log.syslog.enable` → `quarkus.log.syslog.enabled`
      * `quarkus.log.syslog.async.enable` → `quarkus.log.syslog.async.enabled`
      * `quarkus.log.socket.enable` → `quarkus.log.socket.enabled`
      * `quarkus.log.socket.async.enable` → `quarkus.log.socket.async.enabled`
      * `quarkus.snapstart.enable` → `quarkus.snapstart.enabled`
      * `quarkus.smallrye-health.ui.enable` → `quarkus.smallrye-health.ui.enabled`
      * `quarkus.smallrye-graphql.ui.enable` → `quarkus.smallrye-graphql.ui.enabled`
      * `quarkus.smallrye-openapi.enable` → `quarkus.smallrye-openapi.enabled`
      * `quarkus.swagger-ui.enable` → `quarkus.swagger-ui.enabled`

      For more information, see the Quarkus link:https://github.com/quarkusio/quarkus/wiki/Migration-Guide-3.26#enable--enabled-in-configuration-properties-gear-white_check_mark[Migration guide 3.26: `.enable` to `.enabled` in configuration properties]

      // https://issues.redhat.com/browse/QDOCS-1331
      // SME: Guillaume Smet
      // Core
      // Breaking change
      // include::rn/ref_rn-qdocs-1331-enable-to-enabled-in-configuration-properties.adoc[leveloffset=+2]
      Show
      :_mod-docs-content-type: REFERENCE [id="ref_rn-qdocs-1331-enable-to-enabled-in-configuration-properties"] = Configuration: Use `.enabled` instead of `.enable` in configuration properties In the current release, feature toggles in configuration use the `.enabled` suffix instead of `.enable`. This change enhances consistency across configuration properties and prevents the mixing of suffixes. The old `.enable` properties remain recognized for backward compatibility but are deprecated. Run `quarkus update` to automatically migrate your configuration. If you update manually, rename keys such as `quarkus.log.console.enable` to `quarkus.log.console.enabled` to avoid deprecation warnings. Named logging handlers follow the same rule and use `quarkus.log.handler.*."handler-name".enabled`. Impacted properties include: * `quarkus.keycloak.policy-enforcer.enable` → `quarkus.keycloak.policy-enforcer.enabled` * `quarkus.log.console.enable` → `quarkus.log.console.enabled` * `quarkus.log.console.async.enable` → `quarkus.log.console.async.enabled` * `quarkus.log.file.enable` → `quarkus.log.file.enabled` * `quarkus.log.file.async.enable` → `quarkus.log.file.async.enabled` * `quarkus.log.syslog.enable` → `quarkus.log.syslog.enabled` * `quarkus.log.syslog.async.enable` → `quarkus.log.syslog.async.enabled` * `quarkus.log.socket.enable` → `quarkus.log.socket.enabled` * `quarkus.log.socket.async.enable` → `quarkus.log.socket.async.enabled` * `quarkus.snapstart.enable` → `quarkus.snapstart.enabled` * `quarkus.smallrye-health.ui.enable` → `quarkus.smallrye-health.ui.enabled` * `quarkus.smallrye-graphql.ui.enable` → `quarkus.smallrye-graphql.ui.enabled` * `quarkus.smallrye-openapi.enable` → `quarkus.smallrye-openapi.enabled` * `quarkus.swagger-ui.enable` → `quarkus.swagger-ui.enabled` For more information, see the Quarkus link: https://github.com/quarkusio/quarkus/wiki/Migration-Guide-3.26#enable--enabled-in-configuration-properties-gear-white_check_mark [Migration guide 3.26: `.enable` to `.enabled` in configuration properties] // https://issues.redhat.com/browse/QDOCS-1331 // SME: Guillaume Smet // Core // Breaking change // include::rn/ref_rn-qdocs-1331-enable-to-enabled-in-configuration-properties.adoc[leveloffset=+2]
    • Quarkus Docs Sprint 41, Quarkus Docs Sprint 42

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

              Created:
              Updated:
              Resolved: