8000 quarkus runtime options are treated as buildtime options · Issue #39450 · keycloak/keycloak · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
quarkus runtime options are treated as buildtime options #39450
Closed
@Scorpion1091

Description

@Scorpion1091

Before reporting an issue

  • I have read and understood the above terms for submitting issues, and I understand that my issue may be closed without action if I do not follow them.

Area

storage

Describe the bug

We set these parameters in a quarkus.properties file:
quarkus.datasource."user-store".username=${DSC_IAM_JDBC_USER}
quarkus.datasource."user-store".password=${DSC_IAM_JDBC_PWD}
quarkus.datasource."user-store".jdbc.url=${DSC_IAM_JDBC_URL}

According to Quarkus documentation, all 3 are runtime options (no Lock-Symbol):
https://quarkus.io/guides/all-config#quarkus-agroal_quarkus-datasource-jdbc-url
https://quarkus.io/guides/all-config#quarkus-datasource_quarkus-datasource-username
https://quarkus.io/guides/all-config#quarkus-datasource_quarkus-datasource-password

When Starting Keycloak 26.2.2 (probably >26.0.0) following Error occurs and prevent Keycloak from starting:

The following build time options have values that differ from what is persisted - the new values will NOT be used until another build is run: quarkus.datasource."user-store".username, quarkus.datasource."user-store".password, quarkus.datasource."user-store".jdbc.url

Version

26.2.2

Regression

  • The issue is a regression

Expected behavior

The options mentioned in the Error-Message are runtime options and should be treated as such.

Actual behavior

The options mentioned in the Error-Message are falsely treated as buildtime options.

How to Reproduce?

Anything else?

Related Part in Upgrade Guide: https://www.keycloak.org/docs/latest/upgrading/index.html#stricter-startup-behavior-for-build-time-options

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0