In general, I find this --schema-registry-api-key redundant. What would be the use case that you let a consumer, who already has an api key to the topic, read your messages in clear avro text but don't allow him to read the schema.. I guess that's probably the reason why Confluent Cloud seems to have it hidden up now.
I wish these were updates or at least there are some information regarding what's changed. For an example, if I follow this video to how to generate a schema registry api key, I would never find it.
You can generate a schema registry credential in Stream Governance API section (on the right side when you selected environment page) and change cmd flag --sr-api-key to --schema-registry-api-key and --sr-api-secret to --schema-registry-api-secret
What's even more strange, since I didn't find the schema registry api key option, I simply put "confluent kafka topic consume --value-format avro --from-beginning orders", and it worked as well...
@@unboxtronics Even if I follow your instruction by intentionally putting a wrong --schema-registry-api-secret in it, it'll work without promping an error. So how can I tell if my CLI found the schema registry correctly or not...
In general, I find this --schema-registry-api-key redundant. What would be the use case that you let a consumer, who already has an api key to the topic, read your messages in clear avro text but don't allow him to read the schema.. I guess that's probably the reason why Confluent Cloud seems to have it hidden up now.
Thank you for this hands-on example!
Can I make it impossible for producers not to use Schema Registry for a given topic (or for all topics)?
Thanks for your practical insights
API key option is missing in Confluent UI, any help?
I wish these were updates or at least there are some information regarding what's changed. For an example, if I follow this video to how to generate a schema registry api key, I would never find it.
You can generate a schema registry credential in Stream Governance API section (on the right side when you selected environment page)
and change cmd flag --sr-api-key to --schema-registry-api-key and --sr-api-secret to --schema-registry-api-secret
What's even more strange, since I didn't find the schema registry api key option, I simply put "confluent kafka topic consume --value-format avro --from-beginning orders", and it worked as well...
@@unboxtronics Even if I follow your instruction by intentionally putting a wrong --schema-registry-api-secret in it, it'll work without promping an error. So how can I tell if my CLI found the schema registry correctly or not...
Thanks, saved me@@unboxtronics