Skip to content
This repository has been archived by the owner on Nov 12, 2021. It is now read-only.

Policyfile Support for chef-solo provisioner #10

Open
ghost opened this issue Apr 20, 2021 · 1 comment
Open

Policyfile Support for chef-solo provisioner #10

ghost opened this issue Apr 20, 2021 · 1 comment

Comments

@ghost
Copy link

ghost commented Apr 20, 2021

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 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.

@nywilken
Copy link
Contributor

nywilken commented Nov 9, 2021

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.

More details on the plugin archiving process for this provisioner can be found on the Plans to Archive Unmaintained Packer Provisioner Plugins blog post.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant