-
Notifications
You must be signed in to change notification settings - Fork 499
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Issue importing or exporting/downloading spec as YAML (Thorntail platform only) #1925
Comments
This is a classloading issue when deployed in Thorntail (and possibly also Wildfly but I haven't tested that yet). I cannot seem to convince Thorntail to load classes from the application WAR instead of the system. So what's happening is it's loading jackson-databind classes (e.g. We're going to discuss this... |
The solution to this is migrating from Thorntail to Quarkus. We're doing final testing of the Quarkus based images now (in OpenShift) and we could see a new release of Studio as early as next week. There should be no changes needed by anyone deploying Studio. We're just creating new container images using Quarkus instead of Thornail - all of the same configuration env variables should still work. So it should be a drop-in replacement. We'll be updating studio.apicur.io soon after the release to shake out any issues. |
Hi @EricWittmann, Do you have a set timeline by when the next release is expected? |
Hi @lhuria94, the images are available (though not officially released) you can use the tag |
Hoping for next week! |
Reminder: we're going to try and get a release done (using Quarkus) next week (week of Aug 22). In the meantime, anyone can test the latest Quarkus based images using the |
OK we have released version If anyone has time to test out the latest release it would be super helpful. Please note that one big difference between Quarkus and Thorntail is that Quarkus needs to know the database variant (mysql vs. postgresql) at build time. So what this means is that we now have two different container images for each of the
Unfortunately our CI failed when pushing the MySQL variants of the images, so if you're using MySQL you'll need to wait for the next release. If you're using Postgresql the new images should work just like the old ones. |
OK this should now be fixed with the latest release. We're still working on getting the mysql variants pushed to docker hub and quay, but the next release should fix that as well. Also not there is currently a bug with GitHub integration, but that has been fixed and will also be included in the next release. I'm closing this as fixed! |
Hello, i installed apicurio using the operator ( the services are spin up with the latest image tags ) and when i try to use the mocking to Microcks i have this error also i saw that the same error happen when i try to import a Yaml swagger to Apicurio.
The text was updated successfully, but these errors were encountered: