quarkus: ENV Variables doesn't work anymore with Quarkus 0.20.0

Describe the bug I am upgrading quarkus 0.19.1 to 0.20.0.

First kubernetes crash during the Unit tests, but there is already an issue opened.

Secondly, when I launch an “mvn clean install”, the result for my unit test is : … Unknown level “${CONSOLE_LOG_LEVEL:DEBUG}” Caused by: java.lang.IllegalArgumentException: Unknown level “${CONSOLE_LOG_LEVEL:DEBUG}”

It seems there is a regression, and the environment variable is not interpreted/ignored as before.

Then i remove all the env var for my test in applications.properties, but i let the ones for the dev and prod mod. And the result is : [INFO] — quarkus-maven-plugin:0.20.0:build (default) @ backend — [INFO] [io.quarkus.deployment.QuarkusAugmentor] Beginning quarkus augmentation [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal io.quarkus:quarkus-maven-plugin:0.20.0:build (default) on project backend: Failed to build a runnable JAR: Failed to build a runner jar: Failed to augment application classes: Unknown level “${CONSOLE_LOG_LEVEL:DEBUG}” -> [Help 1]

Clearly, it seems that quarkus can’t manage env var and default value anymore.

Configuration

# Add your application.properties here, if applicable.
quarkus.log.console.level=${CONSOLE_LOG_LEVEL:DEBUG}

Environment (please complete the following information):

  • Output of uname -a or ver: Darwin macbook-pro 18.6.0 Darwin Kernel Version 18.6.0: Thu Apr 25 23:16:27 PDT 2019; root:xnu-4903.261.4~2/RELEASE_X86_64 x86_64

  • Output of java -version: java version “11.0.3” 2019-04-16 LTS Java™ SE Runtime Environment 18.9 (build 11.0.3+12-LTS) Java HotSpot™ 64-Bit Server VM 18.9 (build 11.0.3+12-LTS, mixed mode)

  • GraalVM version (if different from Java): N/A

  • Quarkus version or git rev: 0.20.0

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Comments: 20 (14 by maintainers)

Commits related to this issue

Most upvoted comments

The issue is solved with 1.1.0.CR1 many thanks

@dmlloyd should be back from PTO today AFAICS so better ask him the question.

@dmlloyd could you take a look at that one? It’s an important regression that would need fixing before the next release. @elamotte7 provided a reproducer.