Gerrit repo: https://gerrit.wikimedia.org/r/#/admin/projects/wikimedia/TransparencyReport-private
There are some issues with the way Middleman handles link generation and i18n which would be resolved if we use a sub-domain, instead of a directory for the private report. Details in {T175445} (private).
Is there a specific thing you want to achieve with this move? I can do this but would be nice to have on the ticket a tiny bit of reason why this is desired.
Thank you! I'll take this and it should not be a problem . Regarding the private ticket i don't have permissions to read it yet it seems.
Change 415302 had a related patch set uploaded (by Dzahn; owner: Dzahn):
[operations/dns@master] add transparency-private.wikimedia.org
Access is still denied to me on T175445 which is surprising because i'm a member of WMF-NDA and can read security tasks. Is there really a need to lock that down so much more than other things?
Change 415512 had a related patch set uploaded (by Dzahn; owner: Dzahn):
[operations/puppet@production] varnish: add director for transparency-private
There isn't. I am not sure why you can't see the task and I don't have access to change the policy. IIRC, I had requested @Aklapper to make the task visible to all subscribers and I've added you as a subscriber. I think it's a custom policy and will have to be update manually. Sorry I don't have access to do that
T175445 is neither NDA nor Security but custom... Going to https://phabricator.wikimedia.org/maniphest/task/edit/175445/ , "Visible To" was set to "Custom Policy". (Curious: @Prtksxna, can you access that?) Clicking on "Custom Policy", it showed specific user names under "Allow users". I now also added "Allow subscribers".
Maybe the request wasn't to "make the task visible to all subscribers" but to provide access to specific user names? Anyway, hope it works now for @Dzahn.
Change 415512 merged by Dzahn:
[operations/puppet@production] varnish: add director for transparency-private
Change 415912 had a related patch set uploaded (by Dzahn; owner: Dzahn):
[operations/puppet@production] transparency: add/adjust Apache config for private site
Change 415912 merged by Dzahn:
[operations/puppet@production] transparency: add/adjust Apache config for private site
Change 415302 merged by Dzahn:
[operations/dns@master] add transparency-private.wikimedia.org
done!
https://transparency.wikimedia.org (as always)
https://transparency.wikimedia.org/private (now removed)
https://transparency-private.wikimedia.org (now existing and asks for password like /private did before)
@APalmer_WMF @Prtksxna Hi! I just got back to this ticket because we need to move the transparency sites to a new server. Then i found that git-cloning of the "transparency-private" site has been disabled in 2019 in https://phabricator.wikimedia.org/rOPUP0f294613d39d82fdfe2b983b206a99850a8470d6 with a comment by me saying "But we also don't seem to need this site anymore" while it's also not completely removed.
Can you confirm whether we still need https://transparency-private.wikimedia.org or if I can completely remove it?
Mentioned in SAL (#wikimedia-operations) [2020-04-28T08:13:09Z] <mutante> rsyncing transparency-report-private files from bromine to miscweb1002/2002. git-cloning was removed about a year ago but site still exists. need to figure out if it should be deleted (T188362 T247650)
Change 593181 had a related patch set uploaded (by Dzahn; owner: Dzahn):
[operations/puppet@production] remove https://transparency-private.wikimedia.org
Change 593181 merged by Dzahn:
[operations/puppet@production] remove https://transparency-private.wikimedia.org