jiangpengcheng commented on PR #18738:
URL: https://github.com/apache/pulsar/pull/18738#issuecomment-1512537612

   @Anonymitaet 
   
   yes, this is an internal improvement
   
   - yes, we need to tick 2 boxes of `e-2-e` for python
   
   - the `cryptoConfig` is passed via `--input-specs`, so there is no need to 
add a new flag to the reference list
   
   - I see that the `function develop security` means to use secret data in the 
user's function, while this PR is to enable e2e encryption support on the input 
pulsar topics(producer sends encrypted data to pulsar, consumer received 
encrypted data from pulsar and decrypted it) for python runtime, there are 
different, so doesn't need to add examples to it


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to