Anonymitaet commented on a change in pull request #14843:
URL: https://github.com/apache/pulsar/pull/14843#discussion_r834931050



##########
File path: site2/docs/functions-worker.md
##########
@@ -124,8 +124,9 @@ To run function-worker separately, you have to configure 
the following parameter
 
 If authentication is enabled for your broker cluster, you *should* configure 
the authentication plugin and parameters for the functions worker to 
communicate with the brokers.
 
-- `clientAuthenticationPlugin`
-- `clientAuthenticationParameters`
+- `brokerClientAuthenticationEnabled`: Whether to enable the broker client 
authentication used by function workers to talk to brokers.
+- `clientAuthenticationPlugin`: The authentication plugin to be used by the 
pulsar client used in worker service.

Review comment:
       ```suggestion
   - `clientAuthenticationPlugin`: The authentication plugin to be used by the 
Pulsar client used in worker service.
   ```

##########
File path: site2/docs/functions-worker.md
##########
@@ -124,8 +124,9 @@ To run function-worker separately, you have to configure 
the following parameter
 
 If authentication is enabled for your broker cluster, you *should* configure 
the authentication plugin and parameters for the functions worker to 
communicate with the brokers.
 
-- `clientAuthenticationPlugin`
-- `clientAuthenticationParameters`
+- `brokerClientAuthenticationEnabled`: Whether to enable the broker client 
authentication used by function workers to talk to brokers.
+- `clientAuthenticationPlugin`: The authentication plugin to be used by the 
pulsar client used in worker service.
+- `clientAuthenticationParameters`: The authentication parameter to be used by 
the pulsar client used in worker service.

Review comment:
       same




-- 
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