I cannot use the latest Chef Infra Client 15.0.300 with Terraform, it hangs on user acceptance of two product licenses.
provisioner "chef" {
...
version = "15.0.300"
...
}
Acceptance required:
openstack_compute_instance_v2.vm1 (chef): +---------------------------------------------+
openstack_compute_instance_v2.vm1 (chef): Chef License Acceptance
openstack_compute_instance_v2.vm1 (chef): Before you can continue, 2 product licenses
openstack_compute_instance_v2.vm1 (chef): must be accepted. View the license at
openstack_compute_instance_v2.vm1 (chef): https://www.chef.io/end-user-license-agreement/
openstack_compute_instance_v2.vm1 (chef): Licenses that need accepting:
openstack_compute_instance_v2.vm1 (chef): * Chef Infra Client
openstack_compute_instance_v2.vm1 (chef): * Chef InSpec
openstack_compute_instance_v2.vm1 (chef): Do you accept the 2 product licenses (yes/no)?
Hi @mztriz,
I've not been able to try this myself since I don't a Chef environment ready to test against, but I've heard that adding the following configuration will work around this problem:
client_options = [ "chef_license 'accept'" ]
Hi again @mztriz!
I assume your closing this means that the workaround worked! If so, I'm glad. :tada:
I'm going to reopen this to mark that we ought to do _something_ here: at least, we ought to document that this is how to use Chef after a certain version. We might also consider adding a first-class argument for accepting the license, similar to what's proposed in #21345 for the similar problem in Habitat.
Hello! This was released in 0.12.9
https://github.com/hashicorp/terraform/blob/master/CHANGELOG.md#0129-september-17-2019
There is now an accept_license boolean setting.
https://www.terraform.io/docs/provisioners/habitat.html#accept_license-bool-
I'm going to lock this issue because it has been closed for _30 days_ โณ. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Most helpful comment
Hi @mztriz,
I've not been able to try this myself since I don't a Chef environment ready to test against, but I've heard that adding the following configuration will work around this problem: