I need enable CheckUser in beta cluster for testing Global CheckUser related stuff.
if needed, I can disabled for using checkuser for non specified users.
Your pointed tasks are both is targeted to antispam. but this task is not so. I need a testing for Global CheckUser function before directly deploying to production.
Also I can view the User IP address, User Agent , and salted hash password via accessing from ssh.
Krenair is correct, and I also think that enabling CU on Beta is not a great strategy.
There may be other reasons that I am not aware of, but the main reason behind this request is perhaps to have a test platform with some diverse CU data. That, indeed, signifies how poorly the CU code is right now, in terms of unit tests, as well as the need for a maintenance-type script that could populate fake CU data on a test wiki. Instead of working around these, I think the right solution is to augment the code and make it easier for you and future developers to have the ability to test CU without needing to collect real-world data on a test wiki.
Thanks for comment. yeah, we need that. but for now, that solution is not exist and I need a testing in beta site before deploying production.
In my plan, Global CheckUser tool is depends to CentralAuth for finding local user account. WMF setting is not reproducible for easily. I have CentralAuth installed wikis cluster in my development environment, but not complitely reproduce for WMF settings.
On one hand, this is a project management question. Do we want to make an exception (as @Zppix suggested and @Rxy desires), and let this get to the production faster, or do we want to use this bottleneck and require @Rxy to solve this issue (of inability to test CU code easily) once and for all.
I think this issue is chronic enough, and finding an interested and capable programmer (like Rxy) to work on CheckUser is rare enough, that we should not lose the opportunity to solve the testing issue. If we let this one pass by as an exception, it will probably take years until another interest user is stuck in this situation and would realize the importance of creating a script to generate fake data.
On the other hand, it is a privacy consideration. I personally think "we need test data" is not a legitimate use for someone to be given sensitive permissions, as trustworthy as they might be.
@Rxy are you looking for test data to use while testing, or just an environment to test it on?
For the former, could we manufacture test data. We already have makeTestEdits.php, we could modify it to use random IP/XFF info. For the latter, we can set up a cloud VPS project with multiple wikis instead of relying on beta cluster. It wouldn't be identical, but we could install enough extensions to make it close enough for testing purposes. Would that meet your needs?