This message was deleted.

See the

razorsedge-network

module at https://forge.puppet.com/razorsedge/network?src=slack&channel=puppet

This message was deleted.

you have to explicitly declare the removal. So, if you did something like

package { 'foo':
  ensure => 'installed',
}

You have to intentionally remove it:

package { 'foo':
  ensure => 'absent',
}

I did, but it left the other dependency packages

Puppet can’t be responsible for the underlying OS package manager’s operation. All Puppet does is “Hey, OS. Tell your package manager to remove nginx”. After that, it’s out of Puppet’s hands. The OS just says “0" or “1” back to indicate whether the request was succesaful or not

I get it, but I'm new to puppet and am use to Ansible. What is the proper way to completely uninstall a package and its dependencies with Puppet then?

I’m digging through the nginx module to see what it might take as options

same with Ansible. If you use ansible to install nginx and then tell it to remove it, all ansible will do is talk to yum/dnf or apt and do the same thing.

This message was deleted.

You MIGHT get some further help by doing:

class { 'nginx':
  package_ensure => 'absent',
}

Thanks. Where is the best place to find info about the nginx module you were talking about?

first, you can find basic information at forge.puppetlabs.com

Onve you look through the docs on the module, if you’re not getting any joy, you can go to the developer’s git repo and look at the options that the module will take. I’m here: https://github.com/voxpupuli/puppet-nginx/blob/master/manifests/init.pp#L200

I went there to see how Puppet was actually doing the install. The parameter is set to a default of “installed”, so I surmised the opposite

it doesn't understand the option "purge"

"purged"

HAH! I was just about to paste that URL in

But this remove config, not unneeded dependencies.

with purged it does the same thing. Not removing everything.

in my config, unattended-upgrades does remove automatic packages, but it might not fit your use case

@smortex I just want a simple uninstall of package with dependencies is all 🙂 I would have thought this would have been simpler than this.

It's not the way the provider work unfortunately (for good reasons I guess). From a reporting point of view, puppet removing 'foobar' because it is needed by no other packages should be part of managing which resource?

The simple solution is to orchestrate the removal of orphan packages.

Another one is to have a resource that ensure that no package is orphan (exec? hugh 😢)

OK, I figured out "A" solution for now:

node 'puppet.puppetlab.local' {

$packages = ['nginx', 'nginx-core', 'nginx-common']

package { $packages:

ensure => 'purged',

}

service { 'nginx':

ensure => stopped,

enable => false

}

}

Can't you set autoremove policy in /etc/apt/ so it runs every time you interact with apt? Or am I misremembering?

/etc/apt/apt.conf.d/99_local_policy

APT::Install-Recommends "false";
APT::Install-Suggests "false";
APT::Delete-Unused "true";

something like this solves it for everything though might be a bit heavy handed. https://www.debian.org/doc/manuals/aptitude/ch02s05s05.en.html#configAptPurge-Unused if you want to live dangerously. Probably fine for dev environments.