Closed loicgreffier closed 11 months ago
The validation at namespace level could be omitted. All namespaces should have the right to use all the CCloud tags.
A remote validation against Schema Registry API during topic/schema deployment to check that the defined tags are compliant should be performed
Ns4Kafka should provide the ability to tag resources (topics and schemas) with Confluent Cloud tags: https://docs.confluent.io/cloud/current/api.html#tag/Types-(v1)/operation/createTagDefs.
Possible implementation
Users
Users should be able to tag their resources (schemas and topics) when deployed on Confluent Cloud only. The main solution is adding a new field in the resource metadata that contains all the tags split by a comma:
The list of possible tags for a namespace should be defined by admins, and validated at namespace level:
A dedicated executor for tags might need to be implemented to handle both schema tags and topic tags.
Admin
Tags might need to be declared in the Confluent Cloud before getting attached to a resource. In this case, 3 possible solutions:
This option may not make sens in Ns4Kafka as it is unrelated to namespaces at this point.