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
Allow docker inspect
on all types
#23614
Conversation
I should add that this request comes straight from our BDFL. |
Questions :
|
Makes sense to me. |
@vdemeester True! Let me update this sometime today :-) Thanks |
@icecrime I think you can update |
@icecrime @vdemeester I won't do |
f4f6232
to
22bd0a0
Compare
Refactored the code and made it available to inspect all (but nodes!): still requires docker/engine-api#284 to work properly, as cascading between types is based off the ability to identify not found errors. |
308c5ae
to
bc9bc55
Compare
LGTM |
@icecrime needs a rebase |
bc9bc55
to
b3692fc
Compare
Rebased and hopefully good now. |
@icecrime tests are failing 😢 |
b3692fc
to
b16f641
Compare
Thank you all <3 |
services This enhances completion of networks, volumes, plugins, runtimes and local interfaces so that they are consistent with the principles introduced in the completions of nodes and services. This serves as a preparation for implementing bash completion for the enhanced functionality of docker inspeckt (moby#23614). Signed-off-by: Harald Albers <github@albersweb.de>
…rameterized function In moby#23614 `docker inspect` was semantically enhanced to inspect "everything". Therefore moving its logic to `_docker_container_inspect` was not correct. This commit moves it back to its original top-level location (`_docker_inspect`) so that it can be called by `_docker_{container,image}_inspect` and others (will be added in follow-up PRs). Parameterization was added in order to get caller-specific behavior. Signed-off-by: Harald Albers <github@albersweb.de>
Allow top-level
docker inspect
command to inspect any kind of resources. The rationale is thatinspect
already does images and containers for historical reasons, so it might as well support them all. More specialized inspects (e.g.,docker network inspect
) should exist to support type specific options.Depends on docker/engine-api#283.