-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Begin to break up pkg/inspect #3180
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mheon The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
fc20b88
to
73b11c5
Compare
7d23f4b
to
629a1dd
Compare
Remarking for 1.5.0, let's not make gigantic breaking changes in 1.4.0 |
Well, this isn't breaking, but it moves a lot of code around, so we could have broken something |
☔ The latest upstream changes (presumably #2709) made this pull request unmergeable. Please resolve the merge conflicts. |
Alright, let's just get this one in, it's lingering too long. Retagging for 1.4.0 and rebasing. |
Let's put inspect structs where they're actually being used. We originally made pkg/inspect to solve circular import issues. There are no more circular import issues. Image structs remain for now, I'm focusing on container inspect. Signed-off-by: Matthew Heon <matthew.heon@pm.me>
Note to self: image IDs are printed in |
Alright, CI is green. @rhatdan @haircommander @baude @TomSweeneyRedHat @vrothberg @giuseppe PTAL |
LGTM |
@haircommander @baude @TomSweeneyRedHat @vrothberg @giuseppe PTAL |
/lgtm |
Let's put inspect structs where they're actually being used. We originally made pkg/inspect to solve circular import issues. There are no more circular import issues.
Image structs remain for now, I'm focusing on container inspect.
This is Phase 1 of a more comprehensive rework of Inspect, to try and fill in missing fields and make sure what we are printing is sane and consistent with
docker inspect