Skip to content

Upgrade Apicurio Registry from 2.x to 3.x #51008

@carlesarnal

Description

@carlesarnal

Description

There are some required changes already implemented by @ozangunalp. Apart from those, at least the following items are required, adding them here as a checklist to track progress:

  • There are some split packages among Apicurio artifacts.
  • Each time Vert.x instance is retrieved from CDI there is a message logged on INFO :
    INFO [io.apicurio.registry.client.RegistryClientRequestAdapterFactory] (executor-thread-1) Successfully retrieved a Vertx instance from CDI.
  • The image used in Apicurio dev service apicurio/apicurio-registry-mem is no longer maintained in v3. It has to be replaced with apicurio/apicurio-registry
  • There are a bunch of class names in the Quarkus processor for native compilation configuration that possibly no longer exist, we need to clean those up
  • Verify different auth methods including OAuth working in JVM and Native mode
  • Migration guide for config changes etc. + yaml files for quarkus update command

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions