cshamis
commented
5 years ago Concur. A quick way to republish, refresh, replay is the end-goal for the user.
On Aug 20, 2019, at 3:58 PM, Jonathan Meyer notifications@github.com wrote:
Paint Point? Please describe. When I update an image in my registry, I have to manually trigger Silo to re-scan the entire registry before it's discoverable. This can take some time and the feedback on completion is poor.
Desired Solution It would be preferred for Silo to receive notification from a registry when images are pushed. This can be accomplished via the event notification message of Docker Registry: https://docs.docker.com/registry/notifications/
Alternative / Workaround Alternatively we can just ensure all registries are configured to optimize scanning time. This is problematic as it requires us to tune all potential sources for data.
Additional Context The primary goal here is to eliminate any friction in the Seed publish and discovery process. The goal is immediate visibility of newly published images in Scale.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.
Paint Point? Please describe. When I update an image in my registry, I have to manually trigger Silo to re-scan the entire registry before it's discoverable. This can take some time and the feedback on completion is poor.
Desired Solution It would be preferred for Silo to receive notification from a registry when images are pushed. This can be accomplished via the event notification message of Docker Registry: https://docs.docker.com/registry/notifications/
Alternative / Workaround Alternatively we can just ensure all registries are configured to optimize scanning time. This is problematic as it requires us to tune all potential sources for data.
Additional Context The primary goal here is to eliminate any friction in the Seed publish and discovery process. The goal is immediate visibility of newly published images in Scale.