I don’t think there’s any reason to not make that table available, so I assume the only reason it’s not available is that it hasn’t explicitly been made available. I’ll look into this.
|operations/puppet : production||Expose wbqc_constraints view on Wiki Replicas|
|Resolved||Andrew||T170927 Make wbqc_constraints table available on Quarry et al.|
|Resolved||Marostegui||T174182 set up hiwikiversity on labsdb1010|
Adding Security-Team and WMF-Legal for approval of exposing new data. If the data in this table is all available on-wiki to anon users then it should be an easy approval for them. Here is the better description of the data from the gerrit patch:
Make wbqc_constraints table available on Labs
This table is used by the WikibaseQualityConstraints extension to record constraints on Wikidata properties.
Prior to T169647, the table is populated by periodically (every few weeks to months) importing constraints from property talk pages on Wikidata using [ConstraintsFromTemplates], and reading the resulting CSV file into the database using the extension's UpdateConstraintsTable maintenance script.
Following T169647, the table is populated by the constraintsTableUpdate job, which imports constraints from statements on the property entity and is enqueued by a hook that runs when properties are edited.
In both cases, the table is entirely populated from public data, so I believe it can be made available without problems
labsdb1011 will have puppet disable till Monday most likely due to maintenance, but if you let me know the command you'll run on the other labs hosts once the patch is merged, I can take care of labsdb1011 and disable puppet again once I am done there so this task doesn't get blocked on that specific host.