liquibase support setting of liquibase.secureParsing in application.properties #47101
Comments
|
/cc @andrejpetras (liquibase), @geoand (liquibase), @gsmet (liquibase) |
|
Makes sense! Would you like to contribute this? |
|
@geoand I'm really very new to quarkus, maybe 24 hours ;) still trying to find my way around! Doing a technology analysis quarkus vs spring boot - not sure if identifying a bug this early is a +1 😁 so please do not nail me on that this early :) |
|
Of course, no pressure! You likely would have to do something very similar to what we do with the It goes without saying that we are here to help :) |
I wouldn't call us not exposing a configuration that is not recommended a bug. Especially since you can set it from the command line. That being said, I created #47186 but we need to discuss things a bit and polish it before merging. |
|
@gsmet yes, you are right about that. Thanks for your input and work. |
|
@col-panic we added |
|
@gsmet whow - now thats impressive! Thank you very much!! |
Fixes quarkusio#47101 (cherry picked from commit 1f45299)
Describe the bug
This is on quarkus 3.21
Liquibase denies loading a local xsd file and also has problems with http:// urls for loading xsd schemas.
According to liquibase/liquibase#2654 the property
-Dliquibase.secureParsing=falsehas to be set to be allowed to load these files.At the moment I can only add this via
Please extend quarkus-liquibase, resp. the
application.propertiesto include the setting likequarkus.liquibase.secureParsing=falseExpected behavior
No response
Actual behavior
No response
How to Reproduce?
No response
Output of
uname -aorverNo response
Output of
java -versionNo response
Quarkus version or git rev
No response
Build tool (ie. output of
mvnw --versionorgradlew --version)No response
Additional information
No response
The text was updated successfully, but these errors were encountered: