[BUG] CloudEvent not compatible with schema

[joahuber]

[BUG] CloudEvent not compatible with schema

[Netyyyy]

Hi @joahuber . Thank you for reporting this issue. Could you help provide a minimal project? And we will take a look. We appreciate your input and will review this matter as soon as possible.
Please feel free to provide any additional information or context that you think may be helpful. We'll keep you updated on the progress of our review.

[saragluna]

@joshfree should this be an Event Grid related issue?

[joahuber]

@Netyyyy Please find the sample project below. It consists of a single unit test. As soon as you upgrade to version 5.9.0 of the spring-cloud-azure-dependencies dependencies it fails.
CloudEventSample.zip

[Netyyyy]

Hi @joahuber , thanks for your sample. I saw you are using azure-messaging-eventgrid directly which is not managed by spring-cloud-azure-dependencies, so the error is not caused by Spring Cloud Azure and you can remove our bom.
Also, could you check your azure-messaging-eventgrid version? I also encountered this error when upgrading from 4.20.1 to 4.22.1, don't know which version you're using.

@billwert please help take a look

[joahuber]

Hi @Netyyyy
Sorry for the confusion, we do not need azure-messaging-eventgrid (which seems to be managed by your BOM) but only

<dependency>
      <artifactId>azure-core</artifactId>
      <groupId>com.azure</groupId>
</dependency>

which is pulled in as transitive dependency by azure-messaging-eventgrid. It only seems to happen when upgrading to 5.10 of your BOM.

[Netyyyy]

Hi @Netyyyy Sorry for the confusion, we do not need azure-messaging-eventgrid (which seems to be managed by your BOM) but only

<dependency>
      <artifactId>azure-core</artifactId>
      <groupId>com.azure</groupId>
</dependency>

which is pulled in as transitive dependency by azure-messaging-eventgrid. It only seems to happen when upgrading to 5.10 of your BOM.

OK, @alzimmermsft please help take a look, it occurs when using azure-core 1.46

[alzimmermsft]

Hi @joahuber, thanks for reporting this, this definitely did break with the release of azure-core:1.46.0.

Within your application would it be possible to use CloudEvent.fromString which returns List<CloudEvent> as a work around for the time being? Or, if you use our JacksonAdapter.createDefaultSerializerAdapter() it should work as well, as a work around.

I'll look into getting this fixed for future releases of azure-core.