Review main Abandoned

93683[TASK] Use TER REST API for Extension Manager

Benni Mack CR 0 V 0 Hard +916 −39 updated 09/10/26, 08:49

Commit message

This change adds the infrastructure for the Extension Manager
to communicate with the TER via its REST API at
https://extensions.typo3.org/api/v1 instead of importing the weekly
extensions.xml.gz dump into a local database mirror.

Changes in detail:

* Remote\BrowsableRemoteInterface for live queries (search,
  extension details, versions, download URLs) with short-lived caching.
* Remote\TerRestExtensionRemote implementing the new interface and the
  existing ExtensionDownloaderRemoteInterface. Downloads are fetched as
  .zip archives, verified via SHA-256, and extracted using the existing
  ZipService.
* Value objects mirroring the TER REST response schema
  (RemoteExtension, RemoteExtensionVersion, RemoteAuthor,
  RemoteDownloadLinks, RemoteExtensionListResult).
* Remote\RemoteApiPaginator implementing PaginatorInterface on top of a
  REST-paginated response.

All outgoing requests carry a "TYPO3 <version>" User-Agent header so TER
operators can identify the client TYPO3 version.

RemoteRegistry now also tracks browsable remotes and exposes
getBrowsableRemotes() / getDefaultBrowsableRemote(). A browsable remote
takes priority as default remote when registered.

A dedicated cache "extensionmanager_ter_api" is registered to hold API
responses with a short default lifetime (1 hour), replacing the previous
weekly full-dump refresh approach.

Domain\Model\Extension gains a createFromRemoteExtension() factory plus
sha256 / downloadUrl / categoryString fields so existing services and
templates can consume REST-sourced extensions. ExtensionManagementService
prefers the SHA-256 hash and now also triggers downloads for extensions
identified via downloadUrl / sha256.

TerRestExtensionRemote is registered as the new default remote under
identifier "ter_rest", replacing TerExtensionRemote as the default. The
legacy TerExtensionRemote is still shipped but no longer registered as a
remote. ListController is updated in this commit to use the browsable
remote for all catalogue and distribution queries.

Review

  • Code review CR 0
  • Verified V 0
    • core-ci +1 CI

Issues 1

Files 14

Review log 712

  1. Benni Mack uploaded patch set 1 04/15/26, 15:41

  2. core-ci voted on patch set 1 V +1 04/15/26, 15:51 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/100265

  3. Benni Mack marked it ready for review 04/28/26, 12:35

  4. Benni Mack updated the commit message in patch set 2 V +1 04/28/26, 12:51

  5. core-ci voted on patch set 2 V +1 04/28/26, 13:00 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/101213

  6. Benni Mack rebased onto patch set 3 V +1 05/12/26, 17:42

  7. Benni Mack commented on patch set 4 05/12/26, 17:45

    Published edit on patch set 3.
  8. core-ci voted on patch set 3 V +1 05/12/26, 17:52 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/101910

  9. core-ci voted on patch set 4 V +1 05/12/26, 17:53 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/101911

  10. Benni Mack uploaded patch set 5 V +1 05/17/26, 09:59

  11. core-ci voted on patch set 5 V +1 05/17/26, 10:07 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/102097

  12. Benni Mack abandoned the change 09/10/26, 08:49

    wont do