Proxy attachments and build artifacts through Gitlab

If a user wants to download a build artifact or attachment in an issue, gitlab will redirect the request to s3. When using the docker registry, the s3 storage driver serves as a proxy, so Gitlab will fetch the image and fulfill the request. No redirect is involved here (as far as I can see). How could I replicate this behavior for attachments and artifacts?

We are Self-managed running 16.1.2-ee

I have not tried anything besides studying the documentation.

You could upload the files to the generic package registry and reference that from release notes, MR comments, etc.

Hi @dnsmichi Thanks for your reply. Is there a way to make Gitlab redirect attachment uploads to the generic package registry?

Not that I know of. Suggest opening a feature proposal.