Skip to content

Return cached manifest when request fails

Adie (she/her) requested to merge 341954-use-fallback-on-dependency-proxy-timeout into master

What does this MR do and why?

Closes #341954 (closed).

In this MR, we return the cached manifest (if it exists) when the request to fetch the manifest from the external registry fails. This is aligned with how we return the cached manifest as well when an HTTP error happens.

Screenshots or screen recordings

Here is a diagram on how the flow goes and the green circle is is the change in this MR.

If the manifest fetch from the external registry was not successful, we return the cached manifest, if it exists.

C

How to set up and validate locally

The issue lists great ways on how to replicate the problem.

You can replicate the issue by:

  1. Setting the registry to public
  2. Pulling it through the dependency proxy
  3. Then setting the registry to private.

MR acceptance checklist

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

Related to #341954 (closed)

Edited by Adie (she/her)

Merge request reports