-
Notifications
You must be signed in to change notification settings - Fork 394
Tests for the X-Registry-Supports-Signatures extension #256
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
Closed
mtrmac
wants to merge
5
commits into
containers:master
from
mtrmac:x-registry-supports-signatures-tests
Closed
Tests for the X-Registry-Supports-Signatures extension #256
mtrmac
wants to merge
5
commits into
containers:master
from
mtrmac:x-registry-supports-signatures-tests
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
4055fcc to
ba1d0aa
Compare
859c64d to
936827d
Compare
faa0ff4 to
989ddcb
Compare
989ddcb to
0e44572
Compare
a3c6480 to
7400bf5
Compare
bc76afb to
748ff00
Compare
7084eda to
d798f69
Compare
7d4f00a to
ae3e3ce
Compare
0320ab0 to
c6561e5
Compare
48d6951 to
1304b5c
Compare
18def57 to
cf7cfcf
Compare
22b64f9 to
77af62a
Compare
34b2fb3 to
8cff7a2
Compare
8cff7a2 to
93160ce
Compare
a230533 to
bd2c852
Compare
bd2c852 to
d5905ef
Compare
d5905ef to
d32526b
Compare
d32526b to
4d2173a
Compare
Member
|
@mtrmac @vrothberg What should we do with this PR? Should we rebase and move forward or should we close it? |
4d2173a to
ed05ff5
Compare
Collaborator
Author
|
The discussion whether to do this at all should happen in #254. Until then, rebased. |
efadbf5 to
1929f0c
Compare
1929f0c to
a088df4
Compare
a088df4 to
c1733d6
Compare
c2e0b98 to
2b476f8
Compare
2b476f8 to
efe12a0
Compare
efe12a0 to
a35541c
Compare
…er, add an example This allows running the test against a live registry once, manually inspecting the requests/responses to be as expected, and then running all tests against a “recording” of the requests/responses, completely off-line. Also adds a simple test for GetManifest to demonstrate the use of the mechanism. The httpWrapper mechanism is intended purely for tests, and not intended to be exposed to external users; they should use types.SystemContext. Signed-off-by: Miloslav Trmač <mitr@redhat.com>
… at the dockerClient helper level, and in the dockerImageSource case. Does not actually test all of dockerImageSource.GetSignatures (including the support autodetection). Signed-off-by: Miloslav Trmač <mitr@redhat.com>
Signed-off-by: Miloslav Trmač <mitr@redhat.com>
… primarily to test the supportsSignatures parsing, for now; also smoke-tests Bearer challenges and http/https detection. Signed-off-by: Miloslav Trmač <mitr@redhat.com>
a35541c to
b23c3b0
Compare
Collaborator
Author
|
Not valuable enough. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This depends on, and includes, #254 and #255 , and adds tests for the new functionality introduced in #255. This is split from #255 so that the “how to test the docker registry client” discussion is not blocking merging of the code.
See individual commit messages for a bit more detail.