Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define a registry adapter to use when discovery is not possible, i.e. just list the images. #878

Closed
jwmatthews opened this issue Apr 4, 2018 · 0 comments

Comments

@jwmatthews
Copy link
Member

For those cases where a user wants to use the Broker against a Registry that does not support discovery, let's provide a clear option of explicitly listing the images.

Assume we will want to call this adapter something that clearly expresses it is a manual listing of images, i.e. no discovery. User is responsible for listing the desired images to obtain.

Will need documentation to explain that if we lack working adapters for their intended registry choice, then it's possible to fallback to this method manually listing images.

I'm assuming.....that if we have the image name we can speak to the registry to get the manifest and obtain the ServiceBundle spec....unsure if that is always true.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants