Qovery V3 Beta Testing, Define Roles for the Organization Members (API only)...

Written byAlbane Tonnellier

Albane Tonnellier

Albane started as a Product Owner at Qovery and moved to a Product Marketing Manager position, so you can say she is all about the Product.

See all articles

Hi, fellow changelog readers; this week is extra special for us! First, we are starting a brand new quarter, the last one of the year! Second, our V3 console is now in Beta testing, and yes, we are over the moon and can’t wait for all of you to try it out!

On top of that, we delivered a highly expected feature during the last sprint. Can you guess which one it is?

Without further due, let me tell you more about what has been done during the last sprint!

Qovery V3 Beta Testing

Spoiler alert here, or almost 😅 . If you are following the updates, you probably already know that we have been building a brand new console for some months now, and I have the pleasure of telling you that this V3 is currently in Beta testing, so all of you can give it a go! From a better developer experience to more transparency, and after many excellent feedbacks from our Alpha tester, we can’t wait for you to try it.

If you want to know everything about it, I recommend you check out this article.

Another critical piece of information is that our Changelogs will include every V3 update from now on, so make sure you keep an eye open for every new release.

Console V3
Console V3

Define Roles for the Organization Members (API only)

Only accessible via Qovery REST API 1 at the moment; the Roles and Permissions Management System (RBAC) will be accessible via the Qovery V3 web interface for Q4 2022!

As an organization owner, you want to define specific roles for your organization members so that they can reflect their roles, rights and responsibilities within your organization; it’s now possible thanks to this new feature.

For more technical details about it, head to this thread on our forum, where we explain everything.

Websocket support

While we already support WebSockets, the connexion timeout was set at 60 seconds by default which was pretty low; that’s why we decided to add an Advanced Setting to change this parameter.

Feel free to have a look at our documentation for more information.