Configmap without `kube.mp.messaging.incoming.microcks-asyncapi-triggers.bootstrap.servers` key on version 1.14

[jackfrost82]

Describe the bug

The config map for async is created without the value
kube.mp.messaging.incoming.microcks-asyncapi-triggers.bootstrap.servers
on version 1.14.0

Expected behavior

kube.mp.messaging.incoming.microcks-asyncapi-triggers.bootstrap.servers set to Kafka cluster created by microcks installation

Actual behavior

No response

How to Reproduce?

Microcks version or git rev

1.14

Install method (docker-compose, helm chart, operator, docker-desktop extension,...)

Operator on openshift

Additional information

No response

[github-actions]

👋 @jackfrost82

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]

That's actually a very good point! We forgot to report this change here on the operator. Putting it in the next release!