Skip to content

Conversation

@mheon
Copy link
Member

@mheon mheon commented Aug 2, 2019

Right now, podman volume inspect JSON's the internal volume configuration, then prints it.

This is really not healthy from a maintenance perspective - it forces our internal data format to be the same as what we display to the world, and further forces us to maintain the internal format exactly identical to Docker. It's definitely not good practice, and not sustainable as I start to modify the way volumes work to allow for volume plugins and NFS/other filesystem backed volumes.

Make a new internal Inspect function for volumes, and use that instead. This clears the way for further volume enhancements.

@openshift-ci-robot
Copy link
Collaborator

[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

Details 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-robot openshift-ci-robot added approved Indicates a PR has been approved by an approver from all required OWNERS files. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. size/XL labels Aug 2, 2019
mheon added 2 commits August 2, 2019 15:08
Begin to separate the internal structures and frontend for
inspect on volumes. We can't rely on keeping internal data
structures for external presentation - separating presentation
and internal data format is good practice.

Signed-off-by: Matthew Heon <[email protected]>
@openshift-ci-robot openshift-ci-robot added size/L and removed needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. size/XL labels Aug 2, 2019
@mheon
Copy link
Member Author

mheon commented Aug 2, 2019

/retest

@rhatdan
Copy link
Member

rhatdan commented Aug 3, 2019

LGTM
But you seem to have a stacktrace.

@mheon
Copy link
Member Author

mheon commented Aug 15, 2019

@rhatdan
Copy link
Member

rhatdan commented Aug 16, 2019

LGTM

@giuseppe
Copy link
Member

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Aug 19, 2019
@openshift-merge-robot openshift-merge-robot merged commit bd0b05f into containers:master Aug 19, 2019
@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 26, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 26, 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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants