Have a second person who can run Phabricator SQL queries to be provided for quarterly/yearly Phabricator statistics
Closed, DeclinedPublic
Actions

Assigned To

Authored By

	Aklapper
	Apr 12 2023, 8:54 PM

Project Tags

Referenced Files

None

Subscribers

Description

Currently @Aklapper is the only person in the Developer-Advocacy team who can run read-only SQL queries on the Phabricator DB (since T238425).
This is needed

every three months for some data to be shared in the quarterly Technical Community Newsletter (see T334121 for the next edition)
every once a year for publishing some Phabricator and Gerrit end-of-year stats to wikitech-l@ (see T326562 for next edition)

There should be another person on the team who has permissions and the setup and knowledge to do this. Because capacity/bottlenecks.

Implementation

Requires a patch in Gerrit which adds the additional LDAP/shell username to the phabricator-admin group defined in the file modules/admin/data/data.yaml in the repo operations/puppet (since https://gerrit.wikimedia.org/r/c/operations/puppet/+/551268/ )

Details

Related Changes in Gerrit:

	Subject	Author	Repo	Branch	Lines +/-
	data.yaml: Add Tricia Burmeister	Triciaburmeister	operations/puppet	production	+1 -1

Customize query in gerrit

Related Objects

Mentioned In: T338955: Make quarterly and yearly Phabricator statistics / metrics emails have a second recipient
T337388: Automate SQL queries for annual end-of-year Phabricator statistics/metrics on wikitech-l@
T337387: Automate SQL queries for quarterly Phabricator statistics/metrics for Technical Community Newsletter
Mentioned Here: T338955: Make quarterly and yearly Phabricator statistics / metrics emails have a second recipient
T337387: Automate SQL queries for quarterly Phabricator statistics/metrics for Technical Community Newsletter
T337388: Automate SQL queries for annual end-of-year Phabricator statistics/metrics on wikitech-l@
T326562: [January 2024] Publish some Phabricator (and/or Gerrit) end-of-year stats for 2023 to wikitech-l@
T334121: Gather Community metrics 2023 Q2 for Technical Community Newsletter in July 2023

Event Timeline

Aklapper created this task.Apr 12 2023, 8:54 PM

Aklapper triaged this task as Medium priority.

Aklapper moved this task from To triage to Backlog on the Developer-Advocacy board.Apr 12 2023, 8:58 PM

Aklapper edited projects, added: Developer-Advocacy (Apr-Jun 2023); removed: Developer-Advocacy.Apr 13 2023, 11:42 AM

Aklapper updated the task description. (Show Details)

I volunteer to be the second person, will send a patch to add my LDAP.

TBurmeister claimed this task.Apr 13 2023, 12:39 PM

Add me too

Change 912906 had a related patch set uploaded (by Triciaburmeister; author: Triciaburmeister):

[operations/puppet@production] data.yaml: Add Tricia Burmeister

https://gerrit.wikimedia.org/r/912906

gerritbot added a project: Patch-For-Review.Apr 27 2023, 4:26 PM

Change 912906 abandoned by Triciaburmeister:

[operations/puppet@production] data.yaml: Add Tricia Burmeister

Reason:

Find another user who already has shell access to do this

https://gerrit.wikimedia.org/r/912906

TBurmeister reassigned this task from TBurmeister to komla.Apr 27 2023, 4:52 PM

TBurmeister lowered the priority of this task from Medium to Lowest.

There are 2 types of "admins" (users in admin/data.yaml). The first is in the section labelled "ldap_only_admins". That is for users who just have membership in some LDAP group but don't require shell (ssh) access to a server. The second one is for actual shell users.

The thing that is requested here requires actuall shell access. So a user that is already in "ldap_only" needs to move to the other section and have some additional parameters, including an SSH key to be used for login.

Are you aware and comfortable with using ssh and a mysql console?

Also we would need you to create an SSH key and paste the public part here on the ticket please.

I've never used mysql console, and due to uh..upcoming organizational changes it doesn't really make sense for me to have this access in the long-term anyways. Since @komla expressed interest, I think he might be a better fit (and he is much more familiar with ssh and probably mysql console than me).

Maintenance_bot removed a project: Patch-For-Review.Apr 27 2023, 5:12 PM

Allow me two or four weeks here to sort out things a bit more

Aklapper renamed this task from Have a second person in the Developer Advocacy team who can run Phabricator SQL queries to Have a second person who can run Phabricator SQL queries to be provided for quarterly/yearly Phabricator statistics.Apr 28 2023, 4:53 PM

I think my team can help with this.

@Aklapper could this task be automated?

Dzahn moved this task from Incoming to Work in Progress on the Collaboration-Services board.May 22 2023, 3:18 PM

Aklapper mentioned this in T337387: Automate SQL queries for quarterly Phabricator statistics/metrics for Technical Community Newsletter.May 24 2023, 12:35 PM

Aklapper mentioned this in T337388: Automate SQL queries for annual end-of-year Phabricator statistics/metrics on wikitech-l@.

could this task be automated?

Good point. I filed separate tasks for that: T337387: Automate SQL queries for quarterly Phabricator statistics/metrics for Technical Community Newsletter; T337388: Automate SQL queries for annual end-of-year Phabricator statistics/metrics on wikitech-l@.

Still I'd want a second recipient for cron mail though - might repurpose this very task.

LSobanski moved this task from Work in Progress to Consultation on the Collaboration-Services board.Jun 5 2023, 2:01 PM

We resolved the automation tasks:)

Is this now a duplicate of T338955 ?

Dzahn mentioned this in T338955: Make quarterly and yearly Phabricator statistics / metrics emails have a second recipient.Jun 13 2023, 3:17 PM

Indeed, this request for humans is obsoleted by machines taking over in T337387 and more humans in T338955.

Have a second person who can run Phabricator SQL queries to be provided for quarterly/yearly Phabricator statisticsClosed, DeclinedPublicActions