William Theaker

> @williamtheaker can you add the exact version and possibly a link to the Apple source inside the description for completeness? It's only really documented in the man page for...

> @williamtheaker upon further review, perhaps this functionality should go straight to getting a deprecation warning instead so that you will get a direct admonition when using. macOS 11 is...

I couldn't find any examples of previously retired resources for reference. Should I just add `Chef::Log.warn("This resource is deprecated and will be removed in a future #{ChefUtils::Dist::Infra::PRODUCT} release.")` to the...

I realized [previous resource deprecations](https://docs.chef.io/chef_deprecations_client/#all-deprecations) required RFCs (now design proposals) so I've opened one to deprecate this resource in #14278 and will update this PR when (🤞) the proposal is...

> @williamtheaker Can you add a `deprecated 'This resource will be removed in the 19.0 release of Chef as macOS 11 and later no longer support this functionality.'` > >...

I don't see any deprecation warnings in the latest run: https://github.com/chef/chef/actions/runs/8511188038/job/23310320337?pr=14128#step:4:1183 I think we'll need to use `Chef.deprecated :generic, "foo"` no matter what.

👍 sample output from adding this warning to a custom resource. ``` Running handlers: Running handlers complete Deprecation warnings that must be addressed before upgrading to Chef Infra 19: This...

> Ugh, `lib/chef/resources.rb` is loading the `osx_profile` resource, causing those failures on https://buildkite.com/chef-oss/chef-chef-main-verify/builds/17131 Is there something I can do to help fix that?

My concerns are mostly about userland issues, not kernel space file locks, especially as Apple has added TCC restrictions to permissions like App Management, making it increasingly clear that they...

@feld would setting `LocalHostName` to the fqdn property fix this?