quarkus.properties not loaded by default
DonPerinon opened this issue · 0 comments
DonPerinon commented
Hi, I want to report a strange behavior that when the keycloak is deployed using keycloak-quarkus role connection to external infinispan is not working out of the box. Maybe I'm missing something but what I think is that quarkus.properties file is not used by the current configuration of the service. The only workaround for me was specifying of remote store explicitly in the cache-ispn.xml file using <remote-server host="> directive.
Keycloak documentation is saying this.
If an enhancement request is not possible, you can configure the server using raw Quarkus properties:
Create a quarkus.properties file in the conf directory.
Define the required properties in that file.
You can use only a [subset](https://github.com/keycloak/keycloak/blob/main/quarkus/runtime/pom.xml#L17) of the Quarkus extensions that are defined in the [Quarkus documentation](https://quarkus.io/guides/all-config). Also, note these differences for Quarkus properties:
A lock icon for a Quarkus property in the [Quarkus documentation](https://quarkus.io/guides/all-config) indicates a build time property. You run the build command to apply this property. For details about the build command, see the subsequent sections on optimizing Keycloak.
No lock icon for a property in the Quarkus guide indicates a runtime property for Quarkus and Keycloak.
Use the [-cf|--config-file] command line parameter to include that file.