You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 12, 2021. It is now read-only.
Policyfile support should be added to the chef-solo provisioner, similar to how it is supported by the chef-client provisioner. I believe the reason the original PR didn't address the deficiency in the Solo provisioner was due to some uncertainty around using Policyfiles with it. There is an example here on how this works (also illustrating how to use chef export to bundle everything up). Additionally, since chef-solo is now just chef-client in Local Mode, there is definitely support for Policyfiles.
Ideally, it would be nice to be able to use the same control mechanisms in both my provisioning pipeline and my actual production environment.
The text was updated successfully, but these errors were encountered:
With the archival of this repository all open issues will be marked as read-only. If you wish to further discuss this plugin or any of its open issues we invite you to open a discussion on the Packer community forum.
This issue was originally opened by @DWSR as hashicorp/packer#6992. It was migrated here as a result of the Packer plugin split. The original body of the issue is below.
Similar to hashicorp/packer#5574
Policyfile support should be added to the
chef-solo
provisioner, similar to how it is supported by thechef-client
provisioner. I believe the reason the original PR didn't address the deficiency in the Solo provisioner was due to some uncertainty around using Policyfiles with it. There is an example here on how this works (also illustrating how to usechef export
to bundle everything up). Additionally, sincechef-solo
is now justchef-client
in Local Mode, there is definitely support for Policyfiles.Ideally, it would be nice to be able to use the same control mechanisms in both my provisioning pipeline and my actual production environment.
The text was updated successfully, but these errors were encountered: