From eac1ded8d1da80fc5dd3e63916600a09337814ba Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Juan=20Manuel=20P=C3=A9rez?= Date: Thu, 25 Apr 2024 16:38:24 +0200 Subject: [PATCH] Removed reference to subject in pivotal.pro schema registry and using a sample one --- .../03_asyncapi_kafka_specs/b_guidelines.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/asynchronous-api-guidelines/03_asyncapi_kafka_specs/b_guidelines.md b/asynchronous-api-guidelines/03_asyncapi_kafka_specs/b_guidelines.md index 8ac7854..cbb4b98 100644 --- a/asynchronous-api-guidelines/03_asyncapi_kafka_specs/b_guidelines.md +++ b/asynchronous-api-guidelines/03_asyncapi_kafka_specs/b_guidelines.md @@ -211,13 +211,13 @@ components: topic1SchemaValue: schemaFormat: 'application/vnd.apache.avro;version=1.9.0' payload: - $ref: https://pro-fdp-pivotal-schema-registry.api.3stripes.io/subjects/sap_retail_pricing.sap_retail.master.prices-value/versions/latest/schema + $ref: https://sit-fdp-pivotal-schema-registry.api.3stripes.io/subjects/pea_fd_fdp.sample.test-value/versions/latest/schema messages: topic1Payload: $ref: '#/components/schemas/topic1SchemaValue' ``` -**Important note** To have a reference to a real schema, a schema from sap_retail_pricing in pivotal.pro schema registry was used in the spec reference as an example +**Important note** The used schema is a very simple one, it is only used to illustrate how to refer to it. ### Security Schemes