confluent schema-registry subject update

Description

Update subject compatibility or mode.

confluent schema-registry subject update <subject> [flags]

Flags

--compatibility string   Can be BACKWARD, BACKWARD_TRANSITIVE, FORWARD, FORWARD_TRANSITIVE, FULL, FULL_TRANSITIVE, or NONE.
--mode string            Can be READWRITE, READONLY, OR IMPORT.
--api-key string         API key.
--api-secret string      API key secret.
--context string         CLI context name.
--environment string     Environment ID.

--compatibility string   Can be BACKWARD, BACKWARD_TRANSITIVE, FORWARD, FORWARD_TRANSITIVE, FULL, FULL_TRANSITIVE, or NONE.
--mode string            Can be READWRITE, READONLY, OR IMPORT.
--ca-location string     File or directory path to CA certificate(s) to authenticate the schema registry client.
--sr-endpoint string     The URL of the schema registry cluster.
--context string         CLI context name.

Global Flags

-h, --help            Show help for this command.
    --unsafe-trace    Equivalent to -vvvv, but also log HTTP requests and responses which may contain plaintext secrets.
-v, --verbose count   Increase verbosity (-v for warn, -vv for info, -vvv for debug, -vvvv for trace).

Examples

Update subject level compatibility of subject “payments”.

confluent schema-registry subject update payments --compatibility=BACKWARD

Update subject level mode of subject “payments”.

confluent schema-registry subject update payments --mode=READWRITE

Update subject level compatibility of subject “payments”

confluent schema-registry subject update payments --compatibility=BACKWARD --ca-location <ca-file-location> --sr-endpoint <schema-registry-endpoint>

Update subject level mode of subject “payments”

confluent schema-registry subject update payments --mode=READWRITE --ca-location <ca-file-location> --sr-endpoint <schema-registry-endpoint>

See Also