gcloud pubsub schemas validate-message - validate a message against a Pub/Sub schema

gcloud pubsub schemas validate-message--message=MESSAGE--message-encoding=MESSAGE_ENCODING(--schema-name=SCHEMA_NAME    |--type=TYPE (--definition=DEFINITION |--definition-file=PATH_TO_FILE))[GCLOUD_WIDE_FLAG …]

gcloudpubsubschemasvalidate-message--message="{\"key\": \"my-key\"}"--message-encoding=JSON--definition="syntax = 'proto3'; message Message { optional string key = 1; }"--type=PROTOCOL_BUFFER

To validate an equivalent AVRO schema, run:

gcloudpubsubschemasvalidate-message--definition='{ "type": "record", "namespace": "my.ns", "name": "KeyMsg", "fields": [ { "name": "key", "type": "string" } ] }'\--type=AVRO

--message=MESSAGE

The message to validate against the schema.

--message-encoding=MESSAGE_ENCODING

The encoding of the message.MESSAGE_ENCODING must beone of:binary,json.

Schema definition.Exactly one of these must be specified:

--schema-name=SCHEMA_NAME

Name or full path of an existing schema.

Or at least one of these can be specified:

--type=TYPE

Type of inline schema.TYPE must be one of:avro,protocol-buffer.

This flag argument must be specified if any of the other arguments in this groupare specified.

Schema specification.Exactly one of these must be specified:

--definition=DEFINITION

Inline schema definition.

--definition-file=PATH_TO_FILE

File containing schema definition. Use a full or relative path to a local filecontaining the value of definition_file.

Run$gcloud help for details.