And Bolt and PDK.

The most recent puppet-agent 6 and 7 releases added support for macOS 12 x86_64, e.g. https://downloads.puppet.com/mac/puppet7/12/x86_64/index.html We are working on macOS 11 & 12 M1 support, but have been slowed down by a data center move and a reliable CI solution allowing us to test M1 builds. Not sure why bolt and pdk packages aren't there as well. They're handled by different teams. I'll ping some folks

@tuxmea The next release of Bolt (3.23.0) will include support for macOS 12 and drop support for macOS 10.15. We only build Bolt for platforms that have puppet-agent support, and that was added after the latest Bolt release.

Any updates on pdk and puppet monterrey builds for M1? We could REALLY use those packages. And by that, I mean that I jut got my laptop refreshed and without PDK my productivity has absolutely tanked. Most of our developers are in the same boat as most of our x86_64 mac fleet will be refreshed in the next month or so

Nightly puppet agent packages are available now for 6 and 7, eg http://nightlies.puppet.com/downloads/mac/puppet7-nightly/12/arm64/index.html

@John O'Connor has left the channel

Is there anything special that needs to be done to get the macOS agent to run at the default 30 min interval? For Windows and Linux, it seems to do that automatically as part of the install, but on macOS, it will not run unless we add

runinterval

to the config file. Is that expected?

That is not expected. What macOS version and arch? What version of puppet-agent?

ARM, macOS 13.0.1, 7.19

13 isn’t supported yet. Apple may have changed how launched services request to run on a schedule. Thanks for the heads up

What actually controls or sets up that functionality on macOS 12x or older ?

It’s likely going to all depend on launchd. Apple changes things to meet some arbitrary set of guidelines managed by ${nobody_knows}. (This is a former Apple employee complaining) No one would get notification in any official capacity that something was changing. Just like it “happened” to people out there, it “happened” to us. And we’d all open internal tickets because all sorts of things in our departments would break, and we’d have to make quick accommodating changes to bring our stuff back up. I was only there a couple years and I think I remember breaking changes of that nature 3 or 4 times.

@boats has left the channel

@louiem3 has left the channel

@Igar Volan has left the channel

This message was deleted.

Since the Mac is actually just an Open Systems compliant UNIX, most of the usual coding would apply. Outliers would be things like working with Open Directory or digging into the launchd system… generally speaking, Puppet speaks all of it, but you may have a little more legwork to figure out how Puppet does what you need it to do on Mac OS. A lot of the stuff that I’ve had to look into beyond the base level resources, I’ve cobbled together by looking directly at the providers.

has anyone gotten the PDK to install from Homebrew at level 3.2.1? I seem to be stuck at 3.2.0 on Intel

anyone have any advice on loading a user-level launchagent plist?

it seems the sudo invocation puppet exec is using is not accurate

or is there a module i can use for launchd?

This has long since been archived, but it may still work: https://github.com/macadmins/puppet-launchd

Also, several of the main resources in Puppet are “Mac aware”. as per: https://www.puppet.com/docs/puppet/8/types/service.html#service-provider-launchd

updated to the latest Puppet

yeah i think its a really tricky thing to support, even with the wrong sudo invocation it wont work

those support

/System/Library/LaunchDaemons

/System/Library/LaunchAgents

/Library/LaunchDaemons

/Library/LaunchAgents

but the one i need is userlevel at /Users/<user>/Library/LaunchAgents/ ...

really not loving launchd

largely, when I was at Apple, we didn't either. Engineering kept coming out with stuff, and we kept complaining, but they were untouchable

interesting.. yeah i kinda get that impression about a lot of apple stuff. thanks for the help

@CVQuesty has left the channel