You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While trying to update Quarkus from 3.2.9.Final to 3.6 onwards have come across following issue related to config-
Config property expects to have hyphen before digit,
Example in config java file-
public interface ParenttConfig {
interface Id {
String id();
}
interface XChannels {
Id acrossB2b();
}
..........
}
config yaml-
parentt:
x-channels:
across-b2b:
val: xxxxxx
throws an exception on start-up
java.util.NoSuchElementException: SRCFG00014: The config property parentt.x-channels.across-b-2b.val is required but it could not be found in any config source
Expected behavior
'acrossB2b' in java should be accepted as 'across-b2b' from yaml.
Actual behavior
'acrossB2b' in java is expecting to have 'across-b-2b' from yaml.
How to Reproduce?
Custom Yaml config file with a number in the key name, occurs on application start-up.
Output of uname -a or ver
No response
Output of java -version
17.0.7
Quarkus version or git rev
3.6.0
Build tool (ie. output of mvnw --version or gradlew --version)
mvn 3.8.4
Additional information
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
While trying to update Quarkus from 3.2.9.Final to 3.6 onwards have come across following issue related to config-
Config property expects to have hyphen before digit,
Example in config java file-
config yaml-
throws an exception on start-up
Expected behavior
'acrossB2b' in java should be accepted as 'across-b2b' from yaml.
Actual behavior
'acrossB2b' in java is expecting to have 'across-b-2b' from yaml.
How to Reproduce?
Custom Yaml config file with a number in the key name, occurs on application start-up.
Output of
uname -a
orver
No response
Output of
java -version
17.0.7
Quarkus version or git rev
3.6.0
Build tool (ie. output of
mvnw --version
orgradlew --version
)mvn 3.8.4
Additional information
No response
The text was updated successfully, but these errors were encountered: