Update git submodules
* Update plugins/delete-project from branch 'master'
to 79674d9e00f8458a2f4f6d3a91bd032579c3f25c
- Extract the repository deletion logic so it becomes reusable
The code that deletes a repository is generally quite robust and
as such it will be very useful for the pull-replication plugin.
However, the logic is heavily baked into the plugin itself;
it requires archiving settings read from the plugin config, and
deletion listeners to notify downstream systems - both are not
relevant to the pull-replication plugin (or anything else that
might want to just delete a repo).
Extract the repo deletion logic into a `RepositoryDelete` class,
free from any nuances of the delete-project plugin itself, so it
can be reused. The `FilesystemDeleteHandler` is now essentially
delegating everything into that class. I've also taken the
liberty to add a couple of missing tests for the notifying of
downstream systems through the deletion listeners.
Bug: Issue 16730
Change-Id: Ib28dbed344ef8a419cf7c318d0e87aadd7dadd5e
- Merge "Send project-deleted event after project deletion"
- Send project-deleted event after project deletion
Gerrit EventDispatcher has two types of listeners: user restricted or
unrestricted. For the restricted listeners before sending the event
Gerrit checks if user has permission to access the project. This means
that `project-deleted` event will not be delivered to the restricted
listeners because when we send the event project is already removed
so we cannot check permissions anymore.
Bug: Issue 15778
Change-Id: I86386cf8b321a2dcc8a4a8ee6f36815e5c9228a2
diff --git a/plugins/delete-project b/plugins/delete-project
index b183ee5..79674d9 160000
--- a/plugins/delete-project
+++ b/plugins/delete-project
@@ -1 +1 @@
-Subproject commit b183ee5230273670f3235cc5b3cf32562ccfb7ee
+Subproject commit 79674d9e00f8458a2f4f6d3a91bd032579c3f25c
