Skip to content

Remove container indirection in Blob.lazy

Markus Koller requested to merge blob-lazy-project-coupling into master

What does this MR do?

Spotted while working on !31545 (closed):

When working with wiki repositories, we end up doing container.project.repository and using the main project repository, rather than the original wiki repository.

Since Blob.lazy doesn't use the container we can just pass the Repository instance directly.

Does this MR meet the acceptance criteria?

Conformity

Availability and Testing

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

  • [-] Label as security and @ mention @gitlab-com/gl-security/appsec
  • [-] The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
  • [-] Security reports checked/validated by a reviewer from the AppSec team

Merge request reports

Loading