-
Notifications
You must be signed in to change notification settings - Fork 9
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
imageproxy: Add a method to get image configuration #21
Conversation
Depends containers/skopeo#1523 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks sane to me.
2c5eb22
to
a639a65
Compare
OK, I've updated this 🆕 with infrastructure to support runtime matching of the semver, moving new API methods to a new struct. |
We need this for a few reasons: - It has the layer ordering, which we are *currently* ignoring but will probably be important for correctness later - It is the only thing that has extensible metadata that will survive round trips through docker schema 2
a639a65
to
341a3b3
Compare
Tested in concert with ostreedev/ostree-rs-ext#176 |
My OCD didn't allow having a runtime |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
|
||
Ok(r) | ||
} | ||
|
||
/// If the proxy supports at least semver 0.2.3, return a wrapper with methods from that version. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Interesting approach. I can imagine this becoming unwieldy if we have lots of different versions we need to expose. But I guess clients are coupled enough that we can ensure there's not a large skew to maintain.
We need this for a few reasons:
but will probably be important for correctness later
survive round trips through docker schema 2