tree d732c83be706721c9a2a46ab0ba5ec214d938a19
parent cca91c9770a830e8a6bd37f428feb0dbf4a814cb
author Nitzan Gur-Furman <nitzan@google.com> 1709564252 +0100
committer Gerrit Code Review <noreply-gerritcodereview@google.com> 1709564252 +0000

Update git submodules

* Update plugins/delete-project from branch 'stable-3.9'
  to 93038507ff113042bf09ba96d788af43a5deff28
  - Update delete-project plugin following I479588df
    
    Bug: Google b/289357382
    Release-Notes: skip
    Change-Id: Ia047b6a5a66ff605c2e229f26928d7722a155645
    (cherry picked from commit 723264be4256494c45f5ba056e81be2ad25bbe7c)
    
  - Provide less verbose repo delete method
    
    Currently, the repo delete method exposed is too verbose, and forces
    the client to provide parameters for preserving and archiving the repo.
    
    Provide a less verbose method with sensible defaults.
    Annotate the method so its clear it will be used by the pull-
    replication plugin, this will also prevent accidental removal of the
    method impacting the pull-replication plugin.
    
    Bug: Issue 16730
    Change-Id: I50dbcb9a91bf3697b8c7d66db646020d29dae83a
    (cherry picked from commit 0322a37009071da525bfd8569e98538c2e8891d5)
    
  - Add IntelliJ files to gitignore
    
    Change-Id: I7600680cf559314356fc9478e7100918f334b9dd
    (cherry picked from commit 4b173665d13703332a941d9c347c3adddd45fb54)
    
  - 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
    (cherry picked from commit 79674d9e00f8458a2f4f6d3a91bd032579c3f25c)