You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current approach involves iterating over repositories in a registry. This is identified by Stuart as being unscalable and slow in general. Instead access into the repository should be key driven. This may require some rethinking of how components in a release such as module compilation artifacts (single binary for Go, multiple jars for JVM), schemes, etc get linked together.
The text was updated successfully, but these errors were encountered:
fixes#3076
module binaries now stored as blobs (instead of images); enumeration
operations dropped due to inefficiency - deployment workflows do not
need it anyways
---------
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Motivated by this comment:
#2989 (comment)
The current approach involves iterating over repositories in a registry. This is identified by Stuart as being unscalable and slow in general. Instead access into the repository should be key driven. This may require some rethinking of how components in a release such as module compilation artifacts (single binary for Go, multiple jars for JVM), schemes, etc get linked together.
The text was updated successfully, but these errors were encountered: