-
Notifications
You must be signed in to change notification settings - Fork 553
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
Start to sketch internal/oci/remote.SignedImage[Index]
.
#705
Start to sketch internal/oci/remote.SignedImage[Index]
.
#705
Conversation
Mostly opening this to run the automated tests, there are still several pieces that I want to add to this, and it needs unit test coverage for some of the new functionality in Please don't merge this, or scrutinize it too much yet 😅 |
Ok, I think I can explain all of the failures here with a thing I already had on my TODO list, which is nice. tl;dr using I'll fix that after lunch. |
956bf2e
to
54e7fe1
Compare
c3ef61d
to
6c9477a
Compare
internal/oci/remote.SignedImage[Index]
.internal/oci/remote.SignedImage[Index]
.
This follows the pattern GGCR uses for functional `remote.Options`, and starts to define `SignedImage[Index]` methods, which build upon the `Signatures` implementation from a prior change. This also tries to start adopting this pattern a few places, which drops bits of boilerplate (or changes them to functional options). As part of this, I'm combining `FetchSignaturesForImage[Digest]` and tweaking it's signature a bit (no pun intended!), but I think long term we'll just want folks to consume the `remote` package directly themselves. Signed-off-by: Matt Moore <[email protected]>
6c9477a
to
b80d64c
Compare
name: "signature option", | ||
opts: []Option{WithSignatureSuffix(".pig")}, | ||
want: &options{ | ||
SignatureSuffix: ".pig", |
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.
ecdsa signatures end up being pretty small, actually
This follows the pattern GGCR uses for functional
remote.Options
, and starts to defineSignedImage[Index]
methods, which build upon theSignatures
implementation from a prior change.This also tries to start adopting this pattern a few places, which drops bits of boilerplate (or changes them to functional options).
As part of this, I'm combining
FetchSignaturesForImage[Digest]
and tweaking it's signature a bit (no pun intended!), but I think long term we'll just want folks to consume theremote
package directly themselves.Signed-off-by: Matt Moore [email protected]
Ticket Link
Related #666
Release Note