puppet module environment bug?

[James Green]

jamesg@puppet-master:/etc/puppet$ sudo puppet module list --environment tools_office

/etc/puppet/environments/tools_office/modules

└── garethr-docker (v4.1.1)

/etc/puppet/modules

├── AlexCline-dirtree (v0.2.1)

├── AlexCline-fstab (v0.5.4)

[ lots of others ]

Why does puppet list the modules in the other environments? Is it a bug?

Version: 3.8.5

Thanks,

James

[Lowe Schmidt]

/etc/puppet/modules is available for all environments (if I am not mistaken).

--

Lowe Schmidt | +46 723 867 157

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAMH6%2BaymZc6Qqb00Bn_-DBwpfvg6F8iQA2cMWdVV6heRMcjHhQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[James Green]

So when I replace list with upgrade and specify which module within that environment to upgrade, am I expecting that module's dependencies to be upgraded / installed in the common modules? I ask as we got quite the fright what that happened...

I just tested with --modulepath=environments/tools_office/modules and got the expected results for both list and upgrade, but I'm concerned that --environment does not provide equivalent exclusivity for change operations.

James

To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAC-wWcSqjRkbrqQQfrZ6qVJoOHPDJO3i%3DsVuuhJjXVg9W8fJ3w%40mail.gmail.com.