managedmac incompatible with Puppet 4

[dayglojesus]

Due to a number of small but intractable incompatibilities on both server and client, I must pronounce that this module can only be confidently used with Puppet version 3.

Everything from development workflow tests to implementation suffer from a rash of minor issues.

To re-spec these components for Puppet 4 AND maintain backwards compatibility will require development along a distinct branch.

I fully intend to re-integrate the Puppet 4 changes back into master, but until these changes are complete, this module should to be scoped to Puppet version 3.

As such, I have some changes pending that will signify this decision and direct Puppet 4 users to avoid this module.

Reference Issues: #80 #83

[dayglojesus]

Release 0.7.2 scopes the module to >= Puppet 3.7 and <4.0

[jhg03a]

Is there ongoing work to bring this up to puppet 4 somewhere?

[dayglojesus]

Not yet. Sorry, I just have not found the time to start this yet.

[groob]

I spent some time today trying to figure out the issues in #80 and was able to resolve them by editing the providers like so:
#lib/puppet/provider/macauthdb/default.rb

require 'date'
require 'sqlite3' if Puppet.features.sqlite?
require 'cfpropertylist' if Puppet.features.cfpropertylist?

and then also setting

  confine :feature         => :cfpropertylist
  confine :feature         => :sqlite

In the provider where appropriate.
This allows someone to install the gems if they don't exists before sourcing the provider.

[vism810]

Hi dayglojesus. Your module is everything I need to manage Macs, but I have to ask like other people here - is there an ongoing work to update this module to be compatible with Puppet4/5.
Mostly I am interested in the security settings. If not, can you guide me a bit how to get those settings working in Puppet5.
Thanks