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 Dec 5, 2020. It is now read-only.
I am using the provisioner chef {} to provision the ec2 nodes once they are build using provider aws {}. I was wondering after a successful build if I make any changes in the chef attributes and re-run the terraform apply. Will that change be pulled down to the nodes from Chef Server.
Oh, chef-client is not running as daemon service on the nodes. So I was wondering if provisioner chef {} kicks the chef-client every time terraform apply happens?
Please advise.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi There,
I have a question:
I am using the
provisioner chef {}
to provision theec2
nodes once they are build usingprovider aws {}
. I was wondering after a successful build if I make any changes in thechef attributes
and re-run theterraform apply
. Will that change be pulled down to the nodes fromChef Server
.Oh,
chef-client
is not running as daemon service on the nodes. So I was wondering ifprovisioner chef {}
kicks thechef-client
every timeterraform apply
happens?Please advise.
The text was updated successfully, but these errors were encountered: