Closed detjensrobert closed 3 years ago
Sadly I'm going to have to close this out. We have a large number of folks trying to use this today to migrate off pre-12.5 releases. It's sad, but the reality we have.
@tas50 wouldn't those folks be able to stick with an older version of this cookbook to do those migrations?
What's the plan for unified_mode
Chef 17/18 compatibility with this cookbook if this PR is closed? Does unified_mode
work with the legacy LWRPs?
@detjensrobert We can make it work only on systems with unified mode.
@tas50 wouldn’t folks be able to pin to a version that works w/ Chef < 12.5 to use it to migrate? Or am I missing something?
@jeffbyrnes We're trying to build a single cookbook for all releases and pre-12.9 (when custom resources really worked reliably) is a pretty common upgrade path for customers. This cookbook maintains compatibility all the way back to 11.x for that reason.
Ok, makes sense! Thanks.
unified_mode false if defined?(:unified_mode)
is probably the way to solve this
Signed-off-by: Robert Detjens detjensrobert@osuosl.org
Description
Instead of using Chef 11 resource/providers, switch to Chef 12 custom resources. This also enables
unified_mode
for Chef 17 compatibility.Issues Resolved
Fixes #217.
Check List