Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix apicurio regression #23740

Closed
wants to merge 1 commit into from

Conversation

stuartwdouglas
Copy link
Member

Fixes an issue with Apicurio dev services brought about by a recent
refactor. Also aligns the dev service version with the java version.

Fixes an issue with Apicurio dev services brought about by a recent
refactor. Also aligns the dev service version with the java version.
@quarkus-bot quarkus-bot bot added the area/dependencies Pull requests that update a dependency file label Feb 15, 2022
@@ -29,7 +29,7 @@
* The Apicurio Registry image to use.
* Note that only Apicurio Registry 2.x images are supported.
*/
@ConfigItem(defaultValue = "docker.io/apicurio/apicurio-registry-mem:2.1.5.Final")
@ConfigItem(defaultValue = "docker.io/apicurio/apicurio-registry-mem:2.2.0.Final")
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hum, I suppose this has to be defined in this "static" way? Asking because of #23428.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can definitely improve this, although it is outside the scope of this PR.

@edeandrea
Copy link
Contributor

Does this mean that whatever Quarkus version contains this will require an Apicurio 2.2.0.Final instance? Will an app continue to work against an Apicurio 2.1.5.Final instance?

@stuartwdouglas
Copy link
Member Author

It should still work against 2.1.5.Final, I just noticed that the devservice version was not aligned. The real issue is that the REST url base path was not being appended to the property.

@geoand
Copy link
Contributor

geoand commented Feb 16, 2022

This now actually has a conflict because of #23733 going in

@stuartwdouglas
Copy link
Member Author

Looks like this is not needed any more.

@quarkus-bot quarkus-bot bot added the triage/invalid This doesn't seem right label Feb 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/dependencies Pull requests that update a dependency file triage/invalid This doesn't seem right
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants