Hello, I was curious if there was ever discussion on extending Protocol Buffers to include coverage for redaction of a data field?
Specifically, we are looking at the use case of a developer having a keyword available to them that would allow data classification services, logging services, et. al. to be able to read a particular data field as requiring redaction due to core customer content (or other data classification state) and filtering out the contents during archival/transmission/etc. Or if this would be the wrong approach, are there areas that may be the right technical approach to "shift left" the annotation of parameters earlier in the cycle during coding? We are looking at ways to improve the current workflow in GCP which requires us to track and annotate data between RPC services in production using manual annotation from engineers post-development. -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/protobuf/62f1189a-57c7-4738-834a-7435748c0284n%40googlegroups.com.
