Skip to content

datasource is not propagated from child yml from quarkus.config.locations in 3.20.0 #48320

@Sirius-Dour

Description

@Sirius-Dour

Describe the bug

hi
i have root application.yml that has link to child application-build.yml like

quarkus:
  config:
    locations: ...,application-build.yml...

inside this child file i have quarkus.datasource configs
in version 3.15.4 this was working fine
but when i changed to 3.20.0 it started to fail with The default datasource must be configured for Hibernate Reactive on task quarkusAppPartsBuild
if i move quarkus.datasource section up to root application.yml it is working fine

it seems that in 3.20.0 version quarkus.datasource is not propagated from child config files

Expected behavior

datasource should be loaded from child yml file and build should be successful

Actual behavior

build failed with The default datasource must be configured for Hibernate Reactive

How to Reproduce?

move quarkus.datasource section into separate yml file
add link to it in quarkus.config.locations in root application.yml
start quarkusAppPartsBuild task

Output of uname -a or ver

No response

Output of java -version

java version "17.0.11" 2024-04-16 LTS
Java(TM) SE Runtime Environment (build 17.0.11+7-LTS-207)
Java HotSpot(TM) 64-Bit Server VM (build 17.0.11+7-LTS-207, mixed mode, sharing)

Quarkus version or git rev

3.20.0

Build tool (ie. output of mvnw --version or gradlew --version)

------------------------------------------------------------
Gradle 8.7
------------------------------------------------------------

Build time:   2024-03-22 15:52:46 UTC
Revision:     650af14d7653aa949fce5e886e685efc9cf97c10

Kotlin:       1.9.22
Groovy:       3.0.17
Ant:          Apache Ant(TM) version 1.10.13 compiled on January 4 2023
JVM:          17.0.11 (Oracle Corporation 17.0.11+7-LTS-207)
OS:           Windows 10 10.0 amd64

Additional information

No response

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