Skip to content

Adds a project scoped unique file name constraint for Secure Files

Darby Frey requested to merge secure-files-unique-filename into master

What does this MR do and why?

For the current MVC, the runner integration uses this script to read the files from the API and write them to the runner instance. If that script gets two files with the same name, it will overwrite the first one with the second. This change ensures that a project won't be able to have two files with the same name so that, in turn the runner script won't end up in a situation where an overwrite would happen.

Since this feature is not being used by customers yet, I didn't include any sort of migration or backfill task.

For some additional context on this feature please see !77886 (merged) which adds the model and uploader, and !78227 (merged) which adds the API. There is a recorded walkthrough of the feature as well https://youtu.be/eK3FUskHfdo.

Screenshots or screen recordings

These are strongly recommended to assist reviewers and reduce the time to merge your change.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Darby Frey

Merge request reports