puppet module... remove?

[Philip Brown]

Is there really no way to have puppet module, aka puppet-module, remove a module? It doesnt seem to exist in the usage message.
Nor do I see a "show installed" option?

[Kelsey Hightower]

On Thu, May 10, 2012 at 12:35 PM, Philip Brown <ph...@bolthole.com> wrote:

Is there really no way to have puppet module, aka puppet-module, remove a module? It doesnt seem to exist in the usage message.
Nor do I see a "show installed" option?

Philip,

We just updated the module tool and integrated it into Puppet core starting with Puppet 2.7.14. I have also written two blog posts covering some of the features here: 

http://puppetlabs.com/blog/module-of-the-week-puppet-module-tool-part-2

http://puppetlabs.com/blog/module-of-the-week-puppet-module-tool-part-1

 

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/-EjkkYgWMKEJ.
To post to this group, send email to puppet...@googlegroups.com.
To unsubscribe from this group, send email to puppet-users...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.

--
Kelsey Hightower

Developer

Puppet Labs

(678) 4719501

[Gary Larizza]

Philip,

The puppet-module gem behavior has been merged into the core Puppet as of 2.7.14 and includes the functionality you describe.  `puppet help module` should get you the help you need, and `puppet help module uninstall` should describe the action :)

-- 

Gary Larizza

Sent with Sparrow

On Thursday, May 10, 2012 at 9:35 AM, Philip Brown wrote:

Is there really no way to have puppet module, aka puppet-module, remove a module? It doesnt seem to exist in the usage message.
Nor do I see a "show installed" option?

[Philip Brown]

On Thursday, May 10, 2012 9:40:44 AM UTC-7, Gary Larizza wrote:

Philip,

The puppet-module gem behavior has been merged into the core Puppet as of 2.7.14 and includes the functionality you describe.  `puppet help module` should get you the help you need, and `puppet help module uninstall` should describe the action :)

Ah. well, thats good news.... But I thought that the gem was supposed to give equivalent functionality to the new 'core' stuff.

Are you saying then, that the gem "puppet-module" is a dead end, and is becoming basically incompatible, and my only choice is to attempt to convince central change management to update puppet core everywhere?
This would not be a good thing for me :(
 

[Pieter van de Bruggen]

--

You received this message because you are subscribed to the Google Groups "Puppet Users" group.

To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/CCuD4s2KhYQJ.

To post to this group, send email to puppet...@googlegroups.com.
To unsubscribe from this group, send email to puppet-users...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.

The gem should continue to function as it has, but it is no longer the tool we're advocating.  Ongoing development will happen on the version in core, and new functionality is unlikely to be backported.

Having said that, listing your installed modules is as easy as running an `ls` over your modulepath, and removing an installed module is an `rm -r` of the module's directory.

[Nan Liu]

On Thu, May 10, 2012 at 9:43 AM, Philip Brown <ph...@bolthole.com> wrote:
>
>

In case this isn't clear, in master/agent operation, modules only need
to be installed on the master. You don't need to install the
puppet-module tool on every puppet agent and use puppet-module install
command to update the agent. Puppet agents will pluginsync files in
the module lib directory when they contact the master. The agents will
automatically add/remove files as modules are installed/removed from
the puppet master. See:

http://docs.puppetlabs.com/guides/plugins_in_modules.html#enabling-pluginsync

Thanks,

Nan

[David Campos]

From the documentation I have found that, theoretically, I can install a module from a tar ball or zip. I need that feature because I have to configure a master that, at the present time, is stored in an offline machine (it should serve modules, libraries and facts related with our local environment).

When I try to install a puppet module from the tarball, the system tries anyway to connect to the forge... that's correct? How can I prevent it?

[David Campos]

I reply myself... --force is my friend :)

[Pieter van de Bruggen]

The connection to the Forge is being established to try to resolve dependencies; the `--ignore-dependencies` flag (which is implied by `--force`) is what you're looking for.  :)

--

You received this message because you are subscribed to the Google Groups "Puppet Users" group.

To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/SlWYduPB7o8J.

[Randall Hansen]

On Fri, May 11, 2012 at 9:43 AM, Pieter van de Bruggen
<pie...@puppetlabs.com> wrote:

> The connection to the Forge is being established to try to resolve
> dependencies; the `--ignore-dependencies` flag (which is implied by
> `--force`) is what you're looking for.  :)

Do we need a more explicit offline mode of operation? I'm not sure
the docs are good enough for people to see this.

r

[Pieter van de Bruggen]

While we might want to check the Forge for dependencies, not having a network connection shouldn't be an error when installing from a tarball.  That is a bug.

http://projects.puppetlabs.com/issues/13542

At the very least, we should continue unabated if we're installing a tarball without a network connection.  That seems like a bug to me.