Is there an option to be able to import a v3 asyncapi schema file?

[valrandy]

Reason/Context

Hi,

We've recently been trying to integrate microcks testcontainers in our integration test, but ran into the issue of not being to import v3 asyncapi schemas as the resource in the test. Would just like to ask if there is any way to make this work or is there a plan to include this in a future release?

Description

Currently, it seems the microcks testcontainers implementation only supports importing async api v2.6. It would be nice for it to support the latest asyncapi spec - v3 so that there would be no need to keep separate copies of the same asyncapi schema.

Implementation ideas

No response

[github-actions[bot]]

👋 @valrandy

Welcome to the Microcks community! 💖

Thanks and congrats 🎉 for opening your first issue here! Be sure to follow the issue template or please update it accordingly.

📢 If you're using Microcks in your organization, please add your company name to this list. 🙏 It really helps the project to gain momentum and credibility. It's a small contribution back to the project with a big impact.

If you need to know why and how to add yourself to the list, please read the blog post "Join the Microcks Adopters list and Empower the vibrant open source Community 🙌"

Hope you have a great time there!

🌟 ~~~~~~~~~ 🌟

📢 If you like Microcks, please ⭐ star ⭐ our repo to support it!

🙏 It really helps the project to gain momentum and credibility. It's a small contribution back to the project with a big impact.

[lbroudoux]

Hi @valrandy

Thanks for reaching out! AsyncAPI v3 has been supported in Microcks for more than 1 year now. I suspect the problem may come from an import issue with your spec. Can you check if/how it differs from our samples here: https://github.com/microcks/microcks/tree/master/samples ? Otherwise if you can share a simple reproducer...

[valrandy]

Hi @lbroudoux, actually i suspect that it might have something to do with the microcks uber version we are using with testcontainers as we tried the v3 spec on a non uber container and it imported successfully, can we just use the latest version or is there a specific version of uber that works with v3 as well?

[lbroudoux]

Hum ... interesting! Support for AsyncAPI v3 comes with Microcks 1.9.0 so any regular or uber version from this one should work. Are you using the JVM-based or the native compiled uber image? This latest may introduce some changes... Can you extract logs from the Microcks container or share a reproducer?

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity :sleeping:

It will be closed in 30 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. Microcks is a Cloud Native Computing Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience :heart: