This is in context of a former question about influencing downloaded archives created using the API. I would like to deploy some files stored in a GIT repo using the file archive API as ZIP download to customers, with the important point that I would like to influence the name of the created ZIP archive, the contained root directory and stuff. This doesn’t seem to be possible easily, so I’ve investigated available server side hooks and alike. While there seem to be such for interacting with GIT-repos themself, admin maintenance like creating groups etc., I didn’t find anything helpful for my use-case.
What I would need is some server-side hook registering for individual projects or alike and getting triggered on special requests to the API, like when customers request the following URL:
I know of CI/CD, but would like to avoid pre-creating deployment archives and the necessary housekeeping, like deleting old deployments and stuff. Creating the ZIP-archives on-demand was fast enough until now, so I hoped with some kind of hook I could enhance the server-side process to apply my changes on-the-fly somehow. Maybe using some custom GIT ARCHIVE backend or alike.
So, are there any kind of API hooks?