We have a big announcement to make about Apicurio Studio that I hope some people will be interested in.
Studio has been languishing for quite some time without getting the attention it deserves from us (the maintainers/developers). But that is about to change!
We’re announcing the deprecation of Apicurio Studio 0.2 and the beginning of a new line of development for Apicurio Studio 1.0!
KafkaSQL is a popular storage option for Apicurio Registry, introduced in version 2.0.0.Final
. It has become very reliable, despite its higher complexity compared to the SQL storage option. Sadly, no software is immune to bugs, and KafkaSQL is no exception. On the other hand, bugs can be interesting, and the debugging process can provide a great opportunity to learn about Apicurio Registry and KafkaSQL internals. I’ve described one such bug in my previous blog post, titled Resolving a bug in KafkaSQL storage for Apicurio Registry.
A few days ago [1], an Apicurio Registry user reported that some of their Protobuf artifacts went missing after an upgrade from version 2.4.4.Final
to 2.5.5.Final
. They are using the KafkaSQL storage option, and after some investigation it turned out that other storage options are not affected. I’ve decided to write this article to explain the details, but if you are using KafkaSQL storage, please first jump to the Summary section to see if you might be at risk, and then read the Mitigation section for a list of actions you should take to mitigate the problem until we release a fixed version.
Hey everyone, in recent Apicurio Registry versions we’ve introduced support for securing the application using different OpenID Connect (OIDC) servers, and not just Keycloak. In this blog post, I will explain how to configure the application to secure it using Microsoft Azure Active Directory (Azure AD).
One of the major changes introduced in Apicurio Registry 2.x
were improvements in the supported storage options.
We have kept the possibility of using both PostgreSQL database and Kafka to store your data, but the internals of the
storage options have been improved, and in some ways simplified.
We have received great feedback from the users of the new KafkaSQL storage option, but recently several users have reported an interesting bug, that seems to only affect users with the KafkaSQL persistence enabled.
Apicurio Registry 2.x is our latest and greatest release to date. It has plenty of new features but it also comes with some breaking changes from the previous 1.3.x release. In this post we will explore the process to migrate data from Apicurio Registry 1.3.x to Apicurio Registry 2.x.
Because of the breaking changes between 1.3.x and 2.x, there is no automatic upgrade and instead a migration process is required. But don’t worry! We promise the process is not hard.
Hey everyone, in Apicurio Registry 2.0.0. Finally we’ve introduced support for some new security features. In this blog post, I will explain these concepts and show you how to configure them.
OMG we’ve released a new major version of Apicurio Registry! This post will provide an overview of what’s new in this latest release. Read on for details!
Hello everyone and welcome to the new Apicurio project blog! I know that Apicurio has been around for quite some time, and we even had a blog for a few months back at the start. We were so caught up in bootstrapping the project that we let the blog slip into disuse and ended up discarding it.
Well now it’s back! Or we’re here! Or whatever.