Authentication support for transaction perf
- Dominant language
- Java
- Stars
- 15.3k
- Forks
- 3.8k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 160
Description
**Is your enhancement request related to a problem? Please describe.**
Currently, `bin/pulsar-perf transaction` does not support pass authentication params.
So, if the broker side enabled authentication, we are not able to use the transaction perf tool to test transactions.
**Describe the solution you'd like**
Support authentication for transaction perf tool which similar with perf producer and perf consumer does.
Make sure the transaction perf tool can apply the authentication configurations from `client.conf`
Contributor guide
Research direction
Start with the bin/pulsar-perf transaction command and compare how the perf producer and perf consumer accept authentication settings. Trace how client.conf is applied, then verify that transaction perf can use the same authentication configuration when the broker requires authentication.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100