You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we are facing with the issue in CI/CD that terrafrorm produce following log:
Error: kafka schema is not compatible with version :4
on .terraform/modules/kafka_data/modules/service_kafka_data/main.tf line 36, in resource "aiven_kafka_schema" "this":
36: resource "aiven_kafka_schema" "this" {
Error: kafka schema is not compatible with version :4
on .terraform/modules/kafka_data/modules/service_kafka_data/main.tf line 36, in resource "aiven_kafka_schema" "this":
36: resource "aiven_kafka_schema" "this" {
We cannot fastly determine which schema is not compatible with Aiven schema registry. Can you add more verbose output to this error log with an information about schema subject?
The text was updated successfully, but these errors were encountered:
If we do have an error message coming from Aiven API response on an attempt to add a new Kafka Schema TF users should see that, but there is none in your case.
I will have a look if we have another API endpoint or any way to provide more information regarding schema compatibility issues.
After testing Aiven API Kafka Schema validation endpoint, it looks it sends back an error with explanation only in the situation when a user tries to send a broken Avro format and responds with 500 HTTP. But when a user tries to send an incompatible schema, it returns only a boolean compatibility flag, and in case it is false TF users see that generic error message Kafka schema is not compatible with version: %n.
I created a ticket to improve this situation in our internal issue tracker, unfortunately, cannot give you a link. No changes in TF provider itself are necessary, and when this feature will out, all users will immediately benefit from it.
Hello.
Currently we are facing with the issue in CI/CD that terrafrorm produce following log:
We cannot fastly determine which schema is not compatible with Aiven schema registry. Can you add more verbose output to this error log with an information about schema subject?
The text was updated successfully, but these errors were encountered: