@ander You are basically describing ls and I really like it. Something on the line of
cdist ls --typescdist ls --all(default?)cdist ls --manifests
@ander I like it. It reminds me of https://www.cdi.st/manual/latest/man1/cdist-dump.html, but this time for conf directories.
@nico Should we implement such commands as cdist core shell scripts for which cdist python implementation is a wrapper? We can write cdist core part that detects core/support commands. Then new…
Then we can also migrate cdist-dump to cdist dump, as such command.
YES PLEASE
one utility tule rule them all
we have cdist inventory list. ls vs list? make ls as alias? 🤷
for the sake of consistency, we should spell out commands and not use abbrs.
IMHO it should be either cdist find or if it only works on types it should be namespaced.
e.g.
cdist types list
I will add core 'libexec' support for 'libexec' directory under official 'conf' directory. Here, internal binaries/scripts should be placed. I will add core support for detecting such…
Here is my first attempt for supporting libexec and migrating cdist-dump to libexec: 7dddcb794b.
This helper tool does not parse cdist configuration files. Configuration directories should be specifed by command line options and/or CDIST_PATH environment variable.
that's annoying…
@ander I realized that after creating MR for this, that it should be written in python. But then, I wanted to see a reaction :)
And since it shows type info, then it is really a cdist config info…
One question.
What are the advantages of cdist info over maintained man page cdist-types which contains general info about types?
Yes, there are no local types (custom user types), but info…
mentioned in commit 27b682bfe9593a6ba637ff583e6a9de442a81002