Release notes for Red Hat OpenShift Service Registry

Updated -

Red Hat OpenShift Service Registry is a managed cloud service that enables you to store and manage standard event schemas and API designs, and share them across event-driven and API architectures.

These release notes list new features, fixed issues, and other items to note in each release of Red Hat OpenShift Service Registry.


22 November 2022

Fixed issues

This release of Red Hat OpenShift Service Registry fixes the following issue:

  • MGDX-264: rhoas CLI lists a maximum of 20 service accounts
    Previously, if you used the rhoas service-account list command to see a list of service accounts in your organization, the rhoas command-line interface (CLI) showed a maximum of 20 service accounts. This issue is now fixed. Additional options for rhoas service-account list enable you to specify a page number for the output and the number of service accounts that are listed on a page. For more information about these options, enter rhoas service-account list --help in the CLI.

11 October 2022

What’s new

This release of Red Hat OpenShift Service Registry provides the following new features:

  • Change artifact owner
    Administrators or artifact owners can change the owner of a specific schema or API artifact using the Service Registry web console or REST API. For example, you might need to change owner if artifact owner-only authorization is configured, and the owner leaves the organization or the owner account is deleted.

  • Upload artifact from URL
    You can now upload a schema or API artifact from a URL, in addition to the already supported upload from a file. You can upload by using the Service Registry web console or the REST API.

  • Documentation generation for AsyncAPI artifacts
    AsyncAPI artifacts now support the Documentation tab on the artifact details page. This tab displays human-readable documentation that is generated from the AsyncAPI content. This feature was previously available only for OpenAPI artifacts.

  • Option to display JSON as YAML
    For artifact types that are JSON formatted, the Content tab on the artifact details page now supports switching between JSON and YAML.

For more information on these new features, see Managing schemas and APIs using the Service Registry web console.


30 August 2022

What’s new

This release of Red Hat OpenShift Service Registry provides the following new features:

  • New CLI commands for configuring Service Registry instances
    The rhoas command-line interface (CLI) now includes service-registry setting commands to manage the configuration of a Service Registry instance. For more information about these commands and the options you can specify, see the CLI command reference (rhoas).

  • New CLI option to list artifacts in all artifact groups
    The rhoas CLI now includes a new all-groups option for the service-registry artifact list command to list all artifacts in all groups. For more information about this command and its options, see the CLI command reference (rhoas).


19 July 2022

What’s new

This release of Red Hat OpenShift Service Registry provides the following new features:

  • Red Hat OpenShift Application Services now uses Red Hat Single Sign-On
    For Red Hat OpenShift Application Services, service account management is now handled by Red Hat Single Sign-On (SSO). This replaces the dedicated Managed Application Services (MAS) SSO service that Red Hat OpenShift Application Services previously used. If your Service Registry or Kafka clients use SASL/OAuthBearer authentication, you must change the specified token URL to https://sso.redhat.com/auth/realms/redhat-external/protocol/openid-connect/token and restart the clients.

  • Configurable properties for artifacts stored in OpenShift Service Registry
    In the Artifacts page of the OpenShift Service Registry web console, you can now add properties for each artifact as name-value pairs, in addition to the existing support available in the Core Registry REST API.
    For more information, see Managing schemas and APIs using the Service Registry web console.

  • Support for up to 50 service accounts per organization
    For Red Hat OpenShift Application Services, you can now create up to 50 service accounts per organization. Previously, the limit was 5 service accounts per user. You use service accounts to connect and authenticate your applications with Service Registry instances in OpenShift Service Registry and with Kafka instances in OpenShift Streams for Apache Kafka.
    For information about other limits in OpenShift Service Registry, see Red Hat OpenShift Service Registry Service Limits.

  • Support for bursts of requests
    OpenShift Service Registry now supports up to 10 requests per second, with bursts of up to 100 requests per 10 seconds. For more information, see Red Hat OpenShift Service Registry Service Limits.


26 April 2022

What’s new

This release of Red Hat OpenShift Service Registry provides the following new features:

  • Configurable dynamic settings for Service Registry instances
    In the Settings tab of the OpenShift Service Registry web console, you can now customize the instance configuration. For each instance, you can enable or disable various authentication and authorization settings, as well as a legacy compatibility setting.
    For more information, see Managing schemas and APIs using the Service Registry web console.

  • Export and import of Service Registry instance data
    In the Artifacts page of the OpenShift Service Registry web console, you can now export data from one Service Registry instance, and import it into another Service Registry instance. This feature is useful when migrating data to or from other Service Registry instances or on-premises Apicurio Registry instances.
    For more information, see Managing schemas and APIs using the Service Registry web console.

  • Support for Service Registry artifact references using the Core Registry REST API or Maven plug-in
    OpenShift Service Registry now supports artifact references for Avro, JSON Schema, and Protobuf artifact types. You can use artifact references to connect artifacts to other artifacts and maintain relationships between them. For example, you can define a schema in one file, and then reference it from multiple other artifact files. Service Registry can resolve the linked artifacts, and use them to validate message content.
    For more information, see Introduction to Red Hat OpenShift Service Registry.

  • New rule commands in the rhoas CLI
    The rhoas CLI now includes several new commands to add, remove, or modify rules in a Service Registry instance. For the list of new rule commands in the rhoas CLI, see CLI command reference (rhoas).

Fixed issues

This release of Red Hat OpenShift Service Registry fixes the following issue:

  • MGDSR-308: Forward or Full compatibility not supported for Protobuf
    The Protobuf data format now supports Forward and Full compatibility, in addition to the previously supported Backward compatibility.