Emerson Prado

Results 11 comments of Emerson Prado

`ensure_packages` requires all declarations to have the same value for `ensure`. So: `ensure_packages(['ncftp'])` Declares the package with `ensure => present` (default value) and conflicts with former declaration. Either change it...

> Note that 'installed' is the default, not 'present'. I got the information that 'present' is the default from the function [code](https://github.com/puppetlabs/puppetlabs-stdlib/blob/master/lib/puppet/parser/functions/ensure_packages.rb) itself. > I had issues until I switched...

Some basic facts require a big change: - Main entry point for general Wildfly resource changes is defined type [wildfly::resource](https://github.com/voxpupuli/puppet-wildfly/blob/master/manifests/resource.pp), which uses custom resource [wildfly_resource](https://github.com/voxpupuli/puppet-wildfly/blob/master/lib/puppet/type/wildfly_resource.rb) - Moving from HTTP API...

Proposal for code organization: - Provider `wildfly_cli::cli_api` - Validate CLI commands from `command` parameter - Validate results - Provider `wildfly_resource::cli_api` - Check current resource state - Format CLI commands from...

> Still wondering if this dependency should be installed by module and how? IMHO, yes. Maybe we can work on a general solution in [issue 1247](https://github.com/voxpupuli/puppet-nginx/issues/1247).

+1 for "this would happen automatically, within the module". The module requires, and nothing else uses, the package. As a developer, I'd expect Puppet to handle this kind of dependencies....

Which Suse version? I presume it's a recent enough one so it uses systemd. Or was at the time, since the issue is quite old... I hit this error with...

I guess I found the cause: defined types `wildfly::jgroups::stack`, `wildfly::jgroups::stack::tcp`, `wildfly::jgroups::stack::tcpgossip` and `wildfly::jgroups::stack::tcpping` have no `profile` parameter, which is a required information for `wildfly::resource` in domain mode. I confirmed that...

> was this in before, or did i break it while migratin' it to vox? It already happened (long) before.

I am facing this issue in Linux Mint Debian Edition. This uses a quite old clusterssh version, though (older than the one mentioned in this ancient bug report...), but I...