-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Add support for repositories (registry namespaced) on login/logout and push/pull #11054
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
Add support for repositories (registry namespaced) on login/logout and push/pull #11054
Conversation
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: saschagrunert The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
97db102 to
f89d214
Compare
--accept-repositories integration tests--accept-repositories integration tests
|
Test are running towards green. Do we need a c/common release or are we fine vendoring the latest master here @vrothberg? |
I am cool with vendoring commits during development. We just need to make sure to vendor a release before releasing Podman. |
vrothberg
left a comment
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.
besides the doc nit, LGTM
Nice work, @saschagrunert !
f89d214 to
654553b
Compare
654553b to
ea56c96
Compare
|
@containers/podman-maintainers PTAL |
ea56c96 to
ba97692
Compare
|
@rhatdan PTAL at the latest discussion points |
|
I say no option and opt in to new change. IE Breaking change, If we get complaints, then we can add the flag and the ability to manage this in containers/common. |
OK, that requires a new parameter to |
|
Change in c/common: containers/common#700 |
ba97692 to
69de9d4
Compare
|
/hold |
This adds the integration tests for the repository or namespaced registry feature introduced in c/common. Signed-off-by: Sascha Grunert <[email protected]>
69de9d4 to
732ece6
Compare
|
/hold cancel |
|
LGTM |
|
Any opinions on whether Buildah and Skopeo should opt into the new behavior as well? (For the upcoming releases?) [Cc: @TomSweeneyRedHat for possible timing interaction, especially vs. a Buildah release before vendoring into Podman — I don’t think it would be a problem to deliver this CLI change in Podman only to minimize last-minute rush, but I might be mistaken about that.] |
mtrmac
left a comment
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.
Code LGTM, but I’d prefer someone more knowledgeable to check the timing vs. vendor dance and releases.
|
Yes Buildah and Skopeo should also work the same way. |
--accept-repositories integration tests|
Changed the PR title to reflect the actual change. |
Created containers/buildah#3412 and containers/skopeo#1396 as follow-up. |
This adds the integration tests for the repository or namespaced registry feature introduced in c/common.