Issue #11802 has been updated by Pieter van de Bruggen.
* A `show` action is highly desirable; it was left out of v1 in the interest
of expedience.
* There are examples for this in the "inconsistent state" wireframe.
Dependency not installed:
# puppet module list --tree
Missing dependency `backup` (v1.x):
`mylvmbackup` (v1.1.0) requires `backup` (v1.x)
/etc/puppet/modules
└─┬ mylvmbackup (v1.1.0)
├── UNMET DEPENDENCY backup (v1.x)
└─┬ mysql (v1.0.2)
└── puppet (v1.0.1)
/usr/share/puppet/modules (no modules installed)
Broken dependency:
# puppet module list --tree
Module `mylvmbackup` (v1.1.0) requires `backup` (v1.x);
`backup` (v0.9.1) is installed
/etc/puppet/modules
└─┬ mylvmbackup (v1.1.0)
├── backup (v0.9.1) invalid
└─┬ mysql (v1.0.2)
└── puppet (v1.0.1)
/usr/share/puppet/modules (no modules installed)
* Dependencies from other directories is something I haven't gotten into the
wireframes.
As per our discussion:
# puppet module list --tree
/etc/puppet/modules
└─┬ mylvmbackup (v1.1.0)
├── backup (v1.1.0) [/usr/share/puppet/modules]
└─┬ mysql (v1.0.2)
└── puppet (v1.0.1)
/usr/share/puppet/modules
└── backup (v1.1.0)
* In list view (default), directories are output in modulepath order, with an
alphabetical listing of modules "under" each directory. In tree view,
directories are output in modulepath order, with an alphabetical listing of
modules *that are not depended upon by other modules in that directory* under
that. Each of those top level modules then lists its immediate dependencies,
which each list their dependencies and so on. Modules which are depended upon
multiple times in the same tree should appear multiple times; cycles should be
truncated.
* The same module cannot have multiple versions installed to the same
directory; each directory should list the modules (and corresponding versions)
that it actually contains. In the case of multiple distinct installations of
the same module, we may want to print a warning of annotation on latter
instances of the module -- let me check what Puppet's behavior in that case
actually is.
----------------------------------------
Feature #11802: Puppet Module Tool (PMT) should have a list command
https://projects.puppetlabs.com/issues/11802
Author: Kelsey Hightower
Status: Merged - Pending Release
Priority: Normal
Assignee: Matt Robinson
Category:
Target version: 2.7.11
Affected Puppet version:
Keywords: geordi forge pmt
Branch:
The PMT should gain the ability to list installed module and exhibit behavior
as defined in the UX design doc located here:
[UX Design Doc](https://github.com/puppetlabs/ux/tree/geordi/geordi)
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://projects.puppetlabs.com/my/account
--
You received this message because you are subscribed to the Google Groups
"Puppet Bugs" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-bugs?hl=en.
