Main / Family / Chef package
Chef package download
Use the package resource to manage packages. When the package is installed from a local file (such as with RubyGems, dpkg, or RPM Package Manager), the file must be added to the node using the remote_file or cookbook_file resources. This resource is the base resource for several other resources used for package . Support for using file names to install packages (as in yum_package "/bin/sh") is not available because the volume of data required to parse for this is excessive. Note. In many cases, it is better to use the package resource instead of this one. This is because when the package resource is used in a recipe, the chef-client will. 3 Mar At the Chef Community Summit this year, as with all Summits, there was a Hack Day. My hack project was to extend Chef's `package` resource to be able to handle multiple packages at once. Why? There are two primary use-cases: * When provisioning a new system, installing your base set of packages.
require "chef/decorator/lazy_array". require "shellwords". class Chef. class Provider. class Package Chef::Provider. include Chef::Mixin::ShellOut. extend Chef::Mixin::SubclassDirective. # subclasses declare this if they want all their arguments as arrays of packages and names. subclass_directive: use_multipackage_api. 6 Mar As first raised by @mfischer-zd on the mailing list: Chef introduces the ability to install multiple packages simultaneously via the package resource, using the following syntax: When using the new multi-package installation feature of the package resource introduced in Chef , multiple packages can. require "chef/provider/package". require "chef/resource/yum_package". require " chef/mixin/which". require "chef/mixin/shell_out". require "chef/mixin/ get_source_from_package". require "chef/provider/package/yum/python_helper". require "chef/provider/package/yum/version". # the stubs in the YumCache class are still an.
The best practice for chef is to always start with the same "going in" state. If you're deploying to the cloud, I would create an entirely new VM and deploy PHP from scratch. If you don't have that luxury, then you're in a situation where you must maintain two known starting states. (1) No PHP is installed and (2) Old version of . package "sun-java6-jdk" do action:remove end. See display/chef/Resources#Resources-Package. Classes Methods Files. Search: Top Level Namespace · Chef < ObjectTop Level Namespace. ApiClient < ObjectChef. Registration < ObjectChef::ApiClient. ApiClientV1 < ObjectChef. Application < ObjectChef. Apply < ApplicationChef:: Application. Client < ApplicationChef::Application. ExitCode < ObjectChef:: Application.