Chef product version not configurable

[gsreynolds]

Description

Defaulting to the latest version of chef-client is great but should we allow specifying the version of chef-client to install on the target host as well?

chef-apply/lib/chef_apply/action/install_chef.rb

Lines 79 to 87 in 2d6b0d1

	opts = {
	platform_version: platform.release,
	platform: platform.name,
	architecture: platform.arch,
	product_name: "chef",
	product_version: :latest,
	channel: :stable,
	platform_version_compatibility_mode: true,
	}

[tyler-ball]

Thanks @gsreynolds for filing this - we agree this is a needed feature. Checking to see if there is already a similar issue, and if we don't fine one, this will be the one we use to track this!

[tyler-ball]

For future discussions - I think some of the competing concerns here are 1) we don't want users to get stuck on super old versions of Chef Infra Client and pinning allows that, and 2) users have legitimate reasons to pin to Chef Infra Client versions (like upgrading breaks their cookbook)

[gsantandrea]

A flag should also be given to allow the execution of chef-run for airgapped nodes (both the chef workstation and the target node).
Currently chef-run tries to go to the internet site packages.chef.io to retrieve the latest version and does not allow to use a local file.