Skip to content

Conversation

@carlesarnal
Copy link
Member

@carlesarnal carlesarnal commented Nov 7, 2024

This PR upgrades Quarkus with the following additions:

  • We get back to use the datasources created by Quarkus, so any other jdbc property can be configured using standard Quarkus config values.
  • The appropriate datasource is activated at application startup, using the configured storage.
  • It keeps the existing properties for configuring the Apicurio datasource for backwards compatibility, so we technically have two different ways of configuring the same thing, using the apicurio property and using the quarkus one (just one documented). The Apicurio property could be removed, but that would be a breaking change.

@carlesarnal carlesarnal force-pushed the upgrade-quarkus-3-15 branch 2 times, most recently from 3aeda0b to 0ef8e01 Compare November 13, 2024 07:33
@carlesarnal carlesarnal reopened this Nov 14, 2024
@carlesarnal carlesarnal merged commit 1a2a9ea into Apicurio:main Nov 14, 2024
26 of 42 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Support generic JDBC properties Upgrade Registry to use Quarkus 3.15 Connection to Postgres database closed

1 participant