Jakub Senko

Hi, Studio does not currently support adding extension properties using the visual interface, so you'll have to edit the source directly. If we wanted to add this feature, how would...

@EricWittmann I think this could work if Studio supported JSON schemas, and you could separately define a JSON schema for extension properties. That way UI could generate forms based on...

hi, @daida00 version `0.2.49.Final` is running on https://studio.apicur.io/ . Can you please check if the issue has been resolved?

This should be resolved by https://github.com/Apicurio/apicurio-registry-operator/pull/183

From a quick search, it seems that the error is related to the Java module system. The target of reflection must be exposed by the module. Found this issue https://github.com/rhuss/jolokia/issues/394...

I agree with Eric's comment. A few additional thoughts: - Should we perform the download in the request thread? Even if we limit the download size, this feels like a...

There is also a custom metadata properties feature on artifacts and artifact versions, which could be used in a search query. It may not be very efficient to use the...

Hi @mzaikin We have an Apicurio organization in `quay.io` as well, so you can try using `quay.io/apicurio/apicurio-registry-jpa:1.3.2.Final`. The `0.x` Operator supports specifying the image in the CR (as you're doing),...

See also: - https://codeql.github.com/ - https://github.com/github/codeql-action

hi @redsk Are you able to show us the schema you are using? The error happens in the artifact type discovery code, which is not used in the non-compat API...