サクサク読めて、アプリ限定の機能も多数！
トップへ戻る
アメリカ大統領選
docs.chef.io
An environment is a way to map an organization’s real-life workflow to what can be configured and managed when using Chef Infra. This mapping is accomplished by setting attributes and pinning cookbooks at the environment level. With environments, you can change cookbook configurations depending on the system’s designation. For example, by designating different staging and production environments,
Chef Infra is a powerful automation platform that transforms infrastructure into code. Whether you’re operating in the cloud, on-premises, or in a hybrid environment, Chef Infra automates how infrastructure is configured, deployed, and managed across your network, no matter its size. This diagram shows how you develop, test, and deploy your Chef Infra code. Chef Workstation is the location where u
This page is generated from the Chef Infra Client source code. To suggest a change, edit the service.rb file and submit a pull request to the Chef Infra Client repository. All Infra resources page Use the service resource to manage a service. Syntax The full syntax for all of the properties that are available to the service resource is: service 'name' do init_command String options Array, String p
knife is a command-line tool that provides an interface between a local chef-repo and the Chef Infra Server. knife helps users to manage: NodesCookbooks and recipesRoles, Environments, and Data BagsResources within various cloud environmentsThe installation of Chef Infra Client onto nodesSearching of indexed data on the Chef Infra ServerTopicDescription
A knife plugin is a set of one (or more) subcommands that can be added to knife to support additional functionality that is not built-in to the base set of knife subcommands. Many of the knife plugins are built by members of the Chef community and several of them are built and maintained by Chef.The same common options used by knife subcommands can also be used by knife plug-insA knife plugin can
deploy¶ [edit on GitHub] Use the deploy resource to manage and control deployments. This is a popular resource, but is also complex, having the most properties, multiple providers, the added complexity of callbacks, plus four attributes that support layout modifications from within a recipe. The deploy resource is modeled after Capistrano, a utility and framework for executing commands in parallel
This reference describes each of the resources available to Chef Infra Client, including a list of actions, properties, and usage examples. Common FunctionalityThe properties and actions in this section apply to all resources. ActionsThe following actions may be used with any resource: :nothingThis resource block does not act unless notified by another resource to take action. Once notified, this
A resource is a statement of configuration policy that: Describes the desired state for a configuration itemDeclares the steps needed to bring that item to the desired stateSpecifies a resource type—such as package, template, or serviceLists additional details (also known as resource properties), as necessaryAre grouped into recipes, which describe working configurationsResource SyntaxA resource i
Chef Infra Client ships with over 150 built-in resources for managing system configuration such as directory, remote_file, and windows_firewall. With Custom Resources you can extend the built-in capabilities of Chef Infra Client to create reusable resources for use anywhere in your infrastructure. Ship directly in cookbooksLeverage Chef Infra Client built-in resources and any additional custom Rub
Welcome to the Chef Software Documentation! This is the documentation for:
このページを最初にブックマークしてみませんか？
『Chef Documentation』の新着エントリーを見る
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
