Skip to content
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

fix podman pod inspect to support multiple pods #15675

Merged
merged 1 commit into from
Sep 8, 2022

Conversation

Luap99
Copy link
Member

@Luap99 Luap99 commented Sep 7, 2022

Just like the other inspect commands podman pod inspect p1 p2 should return the json for both.

To correctly implement this we follow the container inspect logic, this
allows use to reuse the global inspect command.
Note: To not break the existing single pod output format for podman pod
inspect I added a pod-legacy inspect type. This is only used to make
sure we will print the pod as single json and not an array like for the
other commands. We cannot use the pod type since podman inspect --type
pod did return an array and we should not break that as well.

Fixes #15674

Signed-off-by: Paul Holzinger [email protected]

Does this PR introduce a user-facing change?

podman pod inspect will now correctly work for more than one pod.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 7, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Luap99

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 7, 2022
@mheon
Copy link
Member

mheon commented Sep 7, 2022

Can we return a single pod, and not an array, when only a single pod is returned? Would prevent a break in backwards-compat.

@Luap99
Copy link
Member Author

Luap99 commented Sep 7, 2022

Can we return a single pod, and not an array, when only a single pod is returned? Would prevent a break in backwards-compat.

I think this would be good solution.

Just like the other inspect commands `podman pod inspect p1 p2` should
return the json for both.

To correctly implement this we follow the container inspect logic, this
allows use to reuse the global inspect command.
Note: To not break the existing single pod output format for podman pod
inspect I added a pod-legacy inspect type. This is only used to make
sure we will print the pod as single json and not an array like for the
other commands. We cannot use the pod type since podman inspect --type
pod did return an array and we should not break that as well.

Fixes containers#15674

Signed-off-by: Paul Holzinger <[email protected]>
@Luap99
Copy link
Member Author

Luap99 commented Sep 8, 2022

OK, I think this should work now without breaking changes.

@rhatdan
Copy link
Member

rhatdan commented Sep 8, 2022

LGTM
Should we open an issue to fix this for 5.0?

@Luap99
Copy link
Member Author

Luap99 commented Sep 8, 2022

We can create an issue, I always add a TODO (5.0) comment so I do not forget them.

 $ vgrep 'TODO (5.0)'
Index File                           Line Content
    0 libpod/networking_linux.go:931  931 // TODO (5.0): return the statistics per network interface
    1 pkg/specgen/specgen.go:487      487 // TODO (5.0): change to pointer

@Luap99
Copy link
Member Author

Luap99 commented Sep 8, 2022

@mheon @vrothberg PTAL

Copy link
Member

@vrothberg vrothberg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@vrothberg
Copy link
Member

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Sep 8, 2022
@openshift-merge-robot openshift-merge-robot merged commit eb758c5 into containers:main Sep 8, 2022
@Luap99 Luap99 deleted the pod-inspect branch September 8, 2022 14:38
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 20, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 20, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. release-note
Projects
None yet
Development

Successfully merging this pull request may close these issues.

podman pod inspect not working for more than one argument
5 participants