Pretty much what the title says: we need to take the data generated by #781344: Extend project maintainer UI for manipulating git project ACLs and get it into gitolite, or some other/additional backend used by our git hooks (I speculated on such a possibility here: #714034-56: Determine the access control solution for git).

Comments

sdboyer’s picture

sdboyer commented
Title: Get UI-configured ACLs into gitolite » Make UI-configured ACLs available gitolite/git hooks

Slightly better title

sdboyer’s picture

sdboyer commented
Title: Make UI-configured ACLs available gitolite/git hooks » Make UI-configured ACLs available to gitolite/git hooks

even better without a typo!

sdboyer’s picture

sdboyer commented

Note - sounds like the consensus at the DCSF sprint was that this should be done via drush

sdboyer’s picture

sdboyer commented
Title: Make UI-configured ACLs available to gitolite/git hooks » Make UI-configured ACLs available to gitolite/git-http-backend/git hooks
Project: Drupal.org infrastructure » Version Control / Project* integration
Version: » 6.x-2.x-dev
Component: Git » Code
Priority: Normal » Critical

Moving projects and marking critical. This maybe will actually just end up belonging in vcapi itself as the data will go into the versioncontrol_accounts table, but getting it there will probably need to be done here, in vc_project.

marvil07’s picture

marvil07 commented

As auth is pluggable now on versioncontrol #223891: API change: make authentication management pluggable, AFAIK this is becoming a duplicate of the original issue it should depend on #781344: Extend project maintainer UI for manipulating git project ACLs, as I suppose UI is going to happen there now.

Please correct me if I am wrong, not changing status until other opinion here.

mikey_p’s picture

mikey_p commented
Status: Active » Closed (duplicate)

I think it's fine to close this issue in favor of #781344: Extend project maintainer UI for manipulating git project ACLs.