Nuget package repository ignores s3 prefixes for upload but not download

Summary

A customer reported (internal link) that nuget packages are not pushed to the correct location when pushed, causing issues when trying to download and use.

This seems to be due to the package registry ignoring the the "sub bucket" set.

Steps to reproduce

• Setup object storage with prefix in gitlab_rails['packages_object_store_remote_directory']
• Push nuget package via any means
• Attempt to pull nuget package and get a not found error

What is the current bug behavior?

when pulled the package will not be found and give a 404

What is the expected correct behavior?

package is downloaded correctly

Relevant logs and/or screenshots

see ticket

Possible fixes

from customer:

Luckily, simple copy does the job and I think I will need to implement workaround for it. AWS Lambda function with trigger for package S3 bucket that will grab nuget files and move them to right place as soon as they appear.