vagrant-packet 0.1.2 → 0.1.3

data/vendor/bundle/ruby/2.4.0/bundler/gems/vagrant-04f7215b5e3f/website/source/docs/provisioning/chef_apply.html.md

@@ -1,104 +0,0 @@
----
-layout: "docs"
-page_title: "Chef Apply - Provisioning"
-sidebar_current: "provisioning-chefapply"
-description: |-
-  The Vagrant Chef Apply provisioner allows you to provision the guest using
-  Chef with chef-apply.
----
-
-# Chef Apply Provisioner
-
-**Provisioner name: `chef_apply`**
-
-The Vagrant Chef Apply provisioner allows you to provision the guest using
-[Chef](https://www.getchef.com/), specifically with
-[Chef Apply](https://docs.getchef.com/ctl_chef_apply.html).
-
-Chef Apply is ideal for people who are already experienced with Chef and the
-Chef ecosystem. Specifically, this documentation page does not cover how use
-Chef or how to write Chef recipes.
-
-<div class="alert alert-warning">
-  <strong>Warning:</strong> If you are not familiar with Chef and Vagrant already,
-  we recommend starting with the <a href="/docs/provisioning/shell.html">shell
-  provisioner</a>.
-</div>
-
-## Options
-
-This section lists the complete set of available options for the Chef Apply
-provisioner. More detailed examples of how to use the provisioner are
-available below this section.
-
-* `recipe` (string) - The raw recipe contents to execute using Chef Apply on
-  the guest.
-
-* `log_level` (string) - The log level to use while executing `chef-apply`. The
-  default value is "info".
-
-* `upload_path` (string) - **Advanced!** The location on the guest where the
-  generated recipe file should be stored. For most use cases, it is unlikely you
-  will need to customize this value. The default value is
-  `/tmp/vagrant-chef-apply-#` where `#` is a unique counter generated by
-  Vagrant to prevent collisions.
-
-In addition to all the options listed above, the Chef Apply provisioner supports
-the [common options for all Chef provisioners](/docs/provisioning/chef_common.html).
-
-## Specifying a Recipe
-
-The easiest way to get started with the Chef Apply provisioner is to just
-specify an inline
-[Chef recipe](https://docs.chef.io/recipes.html). For
-example:
-
-```ruby
-Vagrant.configure("2") do |config|
-  config.vm.provision "chef_apply" do |chef|
-    chef.recipe = "package[apache2]"
-  end
-end
-```
-
-This causes Vagrant to run Chef Apply with the given recipe contents. If you are
-familiar with Chef, you know this will install the apache2 package from the
-system package provider.
-
-Since single-line Chef recipes are rare, you can also specify the recipe using a
-"heredoc":
-
-```ruby
-Vagrant.configure("2") do |config|
-  config.vm.provision "chef_apply" do |chef|
-    chef.recipe = <<-RECIPE
-      package "apache2"
-
-      template "/etc/apache2/my.config" do
-        # ...
-      end
-    RECIPE
-  end
-end
-```
-
-Finally, if you would prefer to store the recipe as plain-text, you can set the
-recipe to the contents of a file:
-
-```ruby
-Vagrant.configure("2") do |config|
-  config.vm.provision "chef_apply" do |chef|
-    chef.recipe = File.read("/path/to/my/recipe.rb")
-  end
-end
-```
-
-## Roles
-
-The Vagrant Chef Apply provisioner does not support roles. Please use a
-different Vagrant Chef provisioner if you need support for roles.
-
-## Data Bags
-
-The Vagrant Chef Apply provisioner does not support data_bags. Please use a
-different Vagrant Chef provisioner if you need support for data_bags.

data/vendor/bundle/ruby/2.4.0/bundler/gems/vagrant-04f7215b5e3f/website/source/docs/provisioning/chef_client.html.md

@@ -1,123 +0,0 @@
----
-layout: "docs"
-page_title: "Chef Client - Provisioning"
-sidebar_current: "provisioning-chefclient"
-description: |-
-  The Vagrant Chef Client provisioner allows you to provision the guest using
-  Chef, specifically by connecting to an existing Chef Server and registering
-  the Vagrant machine as a node within your infrastructure.
----
-
-# Chef Client Provisioner
-
-**Provisioner name: `chef_client`**
-
-The Vagrant Chef Client provisioner allows you to provision the guest using
-[Chef](https://www.chef.io/chef/), specifically by connecting
-to an existing Chef Server and registering the Vagrant machine as a
-node within your infrastructure.
-
-If you are just learning Chef for the first time, you probably want
-to start with the [Chef Solo](/docs/provisioning/chef_solo.html)
-provisioner.
-
-<div class="alert alert-warning">
-  <strong>Warning:</strong> If you are not familiar with Chef and Vagrant already,
-  I recommend starting with the <a href="/docs/provisioning/shell.html">shell
-  provisioner</a>.
-</div>
-
-## Authenticating
-
-The minimum required to use provision using Chef Client is to provide
-a URL to the Chef Server as well as the path to the validation key so
-that the node can register with the Chef Server:
-
-```ruby
-Vagrant.configure("2") do |config|
-  config.vm.provision "chef_client" do |chef|
-    chef.chef_server_url = "http://mychefserver.com"
-    chef.validation_key_path = "validation.pem"
-  end
-end
-```
-
-The node will register with the Chef Server specified, download the
-proper run list for that node, and provision.
-
-## Specifying a Run List
-
-Normally, the Chef Server is responsible for specifying the run list
-for the node. However, you can override what the Chef Server sends
-down by manually specifying a run list:
-
-```ruby
-Vagrant.configure("2") do |config|
-  config.vm.provision "chef_client" do |chef|
-    # Add a recipe
-    chef.add_recipe "apache"
-
-    # Or maybe a role
-    chef.add_role "web"
-  end
-end
-```
-
-Remember, this will _override_ the run list specified on the Chef
-server itself.
-
-## Environments
-
-You can specify the [environment](https://docs.chef.io/environments.html)
-for the node to come up in using the `environment` configuration option:
-
-```ruby
-Vagrant.configure("2") do |config|
-  config.vm.provision "chef_client" do |chef|
-    # ...
-
-    chef.environment = "development"
-  end
-end
-```
-
-## Other Configuration Options
-
-There are a few more configuration options available. These generally do not
-need to be modified but are available if your Chef Server requires customization
-of these variables.
-
-* `client_key_path`
-* `node_name`
-* `validation_client_name`
-
-In addition to all the options listed above, the Chef Client provisioner supports
-the [common options for all Chef provisioners](/docs/provisioning/chef_common.html).
-
-## Cleanup
-
-When you provision your Vagrant virtual machine with Chef Server, it creates a
-new Chef "node" entry and Chef "client" entry on the Chef Server, using the
-hostname of the machine. After you tear down your guest machine, Vagrant can be
-configured to do it automatically with the following settings:
-
-```ruby
-chef.delete_node = true
-chef.delete_client = true
-```
-
-If you do not specify it or set it to `false`, you must explicitly delete these
-entries from the Chef Server before you provision a new one with Chef Server.
-For example, using Chef's built-in `knife` tool:
-
-```
-$ knife node delete precise64
-$ knife client delete precise64
-```
-
-If you fail to do so, you will get the following error when Vagrant
-tries to provision the machine with Chef Client:
-
-```
-HTTP Request Returned 409 Conflict: Client already exists.
-```

data/vendor/bundle/ruby/2.4.0/bundler/gems/vagrant-04f7215b5e3f/website/source/docs/provisioning/chef_common.html.md

@@ -1,136 +0,0 @@
----
-layout: "docs"
-page_title: "Common Chef Options - Provisioning"
-sidebar_current: "provisioning-chefcommon"
-description: |-
-  The following options are available to all Vagrant Chef provisioners. Many of
-  these options are for advanced users only and should not be used unless you
-  understand their purpose.
----
-
-# Shared Chef Options
-
-## All Chef Provisioners
-
-The following options are available to all Vagrant Chef provisioners. Many of
-these options are for advanced users only and should not be used unless you
-understand their purpose.
-
-- `binary_path` (string) - The path to Chef's `bin/` directory on the guest
-  machine.
-
-- `binary_env` (string) - Arbitrary environment variables to set before running
-  the Chef provisioner command. This should be of the format `KEY=value` as a
-  string.
-
-- `install` (boolean, string) - Install Chef on the system if it does not exist.
-  The default value is "true", which will use the official Omnibus installer
-  from Chef. This is a trinary attribute (it can have three values):
-
-    - `true` (boolean) - install Chef
-    - `false` (boolean) - do not install Chef
-    - `"force"` (string) - install Chef, even if it is already installed at the
-      proper version on the guest
-
-- `installer_download_path` (string) - The path where the Chef installer will be
-  downloaded to. This option is only honored if the `install` attribute is
-  `true` or `"force"`. The default value is to use the path provided by Chef's
-  Omnibus installer, which varies between releases. This value has no effect on
-  Windows because Chef's omnibus installer lacks the option on Windows.
-
-- `log_level` (string) - The Chef log level. See the Chef docs for acceptable
-  values.
-
-- `product` (string) - The name of the Chef product to install. The default
-  value is "chef", which corresponds to the Chef Client. You can also specify
-  "chefdk", which will install the Chef Development Kit. At the time of this
-  writing, the ChefDK is only available through the "current" channel, so you
-  will need to update that value as well.
-
-- `channel` (string) - The release channel from which to pull the Chef Client
-  or the Chef Development Kit. The default value is `"stable"` which will pull
-  the latest stable version of the Chef Client. For newer versions, or if you
-  wish to install the Chef Development Kit, you may need to change the channel
-  to "current". Because Chef Software floats the versions that are contained in
-  the channel, they may change and Vagrant is unable to detect this.
-
-- `version` (string) - The version of Chef to install on the guest. If Chef is
-  already installed on the system, the installed version is compared with the
-  requested version. If they match, no action is taken. If they do not match,
-  the value specified in this attribute will be installed in favor of the
-  existing version (a message will be displayed).
-  You can also specify "latest" (default), which will install the latest
-  version of Chef on the system. In this case, Chef will use whatever
-  version is on the system. To force the newest version of Chef to be
-  installed on every provision, set the [`install`](#install) option to "force".
-
-- `omnibus_url` (string) - Location of Omnibus installation scripts.
-  This URL specifies the location of install.sh/install.ps1 for
-  Linux/Unix and Windows respectively.
-  It defaults to https://omnitruck.chef.io. The full URL is in this case:
-
-   - Linux/Unix: https://omnitruck.chef.io/install.sh
-   - Windows: https://omnitruck.chef.io/install.ps1
-
-  If you want to have https://example.com/install.sh as Omnibus script
-  for your Linux/Unix installations, you should set this option to
-  https://example.com
-
-## Runner Chef Provisioners
-
-The following options are available to any of the Chef "runner" provisioners
-which include [Chef Solo](/docs/provisioning/chef_solo.html), [Chef Zero](/docs/provisioning/chef_zero.html), and [Chef Client](/docs/provisioning/chef_client.html).
-
-* `arguments` (string) - A list of additional arguments to pass on the
-  command-line to Chef. Since these are passed in a shell-like environment,
-  be sure to properly quote and escape characters if necessary. By default,
-  no additional arguments are sent.
-
-* `attempts` (int) - The number of times Chef will be run if an error occurs.
-  This defaults to 1. This can be increased to a higher number if your Chef
-  runs take multiple runs to reach convergence.
-
-* `custom_config_path` (string) - A path to a custom Chef configuration local
-  on your machine that will be used as the Chef configuration. This Chef
-  configuration will be loaded _after_ the Chef configuration that Vagrant
-  generates, allowing you to override anything that Vagrant does. This is
-  also a great way to use new Chef features that may not be supported fully
-  by Vagrant's abstractions yet.
-
-* `encrypted_data_bag_secret_key_path` (string) - The path to the secret key
-  file to decrypt encrypted data bags. By default, this is not set.
-
-* `environment` (string) - The environment you want the Chef run to be
-  a part of.
-
-* `formatter` (string) - The formatter to use for output from Chef.
-
-* `http_proxy`, `http_proxy_user`, `http_proxy_pass`, `no_proxy` (string) - Settings
-  to configure HTTP and HTTPS proxies to use from Chef. These settings are
-  also available with `http` replaced with `https` to configure HTTPS proxies.
-
-* `json` (hash) - Custom node attributes to pass into the Chef run.
-
-* `log_level` (string) - The log level for Chef output. This defaults to
-  "info".
-
-* `node_name` (string) - The node name for the Chef Client. By default this
-  will be your hostname.
-
-* `provisioning_path` (string) - The path on the remote machine where Vagrant
-  will store all necessary files for provisioning such as cookbooks, configurations,
-  etc. This path must be world writable. By default this is
-  `/tmp/vagrant-chef-#` where "#" is replaced by a unique counter.
-
-* `run_list` (array) - The run list that will be executed on the node.
-
-* `file_cache_path` and `file_backup_path` (string) - Paths on the remote
-  machine where files will be cached and backed up. It is useful sometimes
-  to configure this to a synced folder address so that this can be shared
-  across many Vagrant runs.
-
-* `verbose_logging` (boolean) - Whether or not to enable the Chef
-  `verbose_logging` option. By default this is false.
-
-* `enable_reporting` (boolean) - Whether or not to enable the Chef
-  `enable_reporting` option. By default this is true.

data/vendor/bundle/ruby/2.4.0/bundler/gems/vagrant-04f7215b5e3f/website/source/docs/provisioning/chef_solo.html.md

@@ -1,202 +0,0 @@
----
-layout: "docs"
-page_title: "Chef Solo - Provisioning"
-sidebar_current: "provisioning-chefsolo"
-description: |-
-  The Vagrant Chef Solo provisioner allows you to provision the guest using
-  Chef, specifically with chef-solo.
----
-
-# Chef Solo Provisioner
-
-**Provisioner name: `chef_solo`**
-
-The Vagrant Chef Solo provisioner allows you to provision the guest using
-[Chef](https://www.chef.io/chef/), specifically with
-[Chef Solo](https://docs.chef.io/chef_solo.html).
-
-Chef Solo is ideal for people who are already experienced with Chef,
-already have Chef cookbooks, or are looking to learn Chef. Specifically,
-this documentation page will not go into how to use Chef or how to write
-Chef cookbooks, since Chef is a complete system that is beyond the scope
-of a single page of documentation.
-
-<div class="alert alert-warning">
-  <strong>Warning:</strong> If you are not familiar with Chef and Vagrant already,
-  I recommend starting with the <a href="/docs/provisioning/shell.html">shell
-  provisioner</a>. However, if you are comfortable with Vagrant already, Vagrant
-  is the best way to learn Chef.
-</div>
-
-## Options
-
-This section lists the complete set of available options for the Chef Solo
-provisioner. More detailed examples of how to use the provisioner are
-available below this section.
-
-* `cookbooks_path` (string or array) - A list of paths to where cookbooks
-  are stored. By default this is "cookbooks", expecting a cookbooks folder
-  relative to the Vagrantfile location.
-
-* `data_bags_path` (string or array) - A path where data bags are stored. By
-  default, no data bag path is set. Chef 12 or higher is required to use the
-  array option. Chef 11 and lower only accept a string value.
-
-* `environments_path` (string) - A path where environment definitions are
-  located. By default, no environments folder is set.
-
-* `nodes_path` (string or array) - A list of paths where node objects (in JSON format) are stored. By default, no
-  nodes path is set.
-
-* `environment` (string) - The environment you want the Chef run to be
-  a part of. This requires Chef 11.6.0 or later, and that `environments_path`
-  is set.
-
-* `recipe_url` (string) - URL to an archive of cookbooks that Chef will download
-  and use.
-
-* `roles_path` (string or array) - A list of paths where roles are defined.
-  By default this is empty. Multiple role directories are only supported by
-  Chef 11.8.0 and later.
-
-* `synced_folder_type` (string) - The type of synced folders to use when
-  sharing the data required for the provisioner to work properly. By default
-  this will use the default synced folder type. For example, you can set this
-  to "nfs" to use NFS synced folders.
-
-In addition to all the options listed above, the Chef Solo provisioner supports
-the [common options for all Chef provisioners](/docs/provisioning/chef_common.html).
-
-## Specifying a Run List
-
-The easiest way to get started with the Chef Solo provisioner is to just
-specify a [run list](https://docs.chef.io/nodes.html#about-run-lists). This looks like:
-
-```ruby
-Vagrant.configure("2") do |config|
-  config.vm.provision "chef_solo" do |chef|
-    chef.add_recipe "apache"
-  end
-end
-```
-
-This causes Vagrant to run Chef Solo with the "apache" cookbook. The cookbooks
-by default are looked for in the "cookbooks" directory relative to your
-project root. The directory structure ends up looking like this:
-
-```
-$ tree
-.
-|-- Vagrantfile
-|-- cookbooks
-|   |-- apache
-|       |-- recipes
-|           |-- default.rb
-```
-
-The order of the calls to `add_recipe` will specify the order of the run list.
-Earlier recipes added with `add_recipe` are run before later recipes added.
-
-## Custom Cookbooks Path
-
-Instead of using the default "cookbooks" directory, a custom cookbooks
-path can also be set via the `cookbooks_path` configuration directive:
-
-```ruby
-Vagrant.configure("2") do |config|
-  config.vm.provision "chef_solo" do |chef|
-    chef.cookbooks_path = "my_cookbooks"
-  end
-end
-```
-
-The path can be relative or absolute. If it is relative, it is relative
-to the project root.
-
-The configuration value can also be an array of paths:
-
-```ruby
-Vagrant.configure("2") do |config|
-  config.vm.provision "chef_solo" do |chef|
-    chef.cookbooks_path = ["cookbooks", "my_cookbooks"]
-  end
-end
-```
-
-## Roles
-
-Vagrant also supports provisioning with [Chef roles](https://docs.chef.io/roles.html).
-This is done by specifying a path to a roles folder where roles are defined
-and by adding roles to your run list:
-
-```ruby
-Vagrant.configure("2") do |config|
-  config.vm.provision "chef_solo" do |chef|
-    chef.roles_path = "roles"
-    chef.add_role("web")
-  end
-end
-```
-
-Just like the cookbooks path, the roles path is relative to the project
-root if a relative path is given.
-
-The configuration value can also be an array of paths on Chef 11.8.0 and newer.
-On older Chef versions only the first path is used.
-
-**Note:** The name of the role file must be the same as the role name.
-For example the `web` role must be in the `roles_path` as web.json or web.rb.
-This is required by Chef itself, and is not a limitation imposed by
-Vagrant.
-
-## Data Bags
-
-[Data bags](https://docs.chef.io/data_bags.html) are also
-supported by the Chef Solo provisioner. This is done by specifying
-a path to your data bags directory:
-
-```ruby
-Vagrant.configure("2") do |config|
-  config.vm.provision "chef_solo" do |chef|
-    chef.data_bags_path = "data_bags"
-  end
-end
-```
-
-## Custom JSON Data
-
-Additional configuration data for Chef attributes can be passed in
-to Chef Solo. This is done by setting the `json` property with a Ruby
-hash (dictionary-like object), which is converted to JSON and passed
-in to Chef:
-
-```
-Vagrant.configure("2") do |config|
-  config.vm.provision "chef_solo" do |chef|
-    # ...
-
-    chef.json = {
-      "apache" => {
-        "listen_address" => "0.0.0.0"
-      }
-    }
-  end
-end
-```
-
-Hashes, arrays, etc. can be used with the JSON configuration object. Basically,
-anything that can be turned cleanly into JSON works.
-
-## Custom Node Name
-
-You can specify a custom node name by setting the `node_name` property. This
-is useful for cookbooks that may depend on this being set to some sort
-of value. Example:
-
-```ruby
-Vagrant.configure("2") do |config|
-  config.vm.provision "chef_solo" do |chef|
-    chef.node_name = "foo"
-  end
-end
-```

data/vendor/bundle/ruby/2.4.0/bundler/gems/vagrant-04f7215b5e3f/website/source/docs/provisioning/chef_zero.html.md

@@ -1,92 +0,0 @@
----
-layout: "docs"
-page_title: "Chef Zero - Provisioning"
-sidebar_current: "provisioning-chefzero"
-description: |-
-  The Vagrant Chef Zero provisioner allows you to provision the guest using
-  Chef, specifically with chef-zero.
----
-
-# Chef Zero Provisioner
-
-**Provisioner name: `chef_zero`**
-
-The Vagrant Chef Zero provisioner allows you to provision the guest using
-[Chef](https://www.getchef.com/chef/), specifically with
-[Chef Zero/local mode](https://docs.getchef.com/ctl_chef_client.html#run-in-local-mode).
-
-This new provisioner is a middle ground between running a full blown
-Chef Server and using the limited [Chef Solo](/docs/provisioning/chef_solo.html)
-provisioner. It runs a local in-memory Chef Server and fakes the validation
-and client key registration.
-
-<div class="alert alert-warning">
-  <strong>Warning:</strong> If you are not familiar with Chef and Vagrant already,
-  I recommend starting with the <a href="/docs/provisioning/shell.html">shell
-  provisioner</a>. However, if you are comfortable with Vagrant already, Vagrant
-  is the best way to learn Chef.
-</div>
-
-## Options
-
-This section lists the complete set of available options for the Chef Zero
-provisioner. More detailed examples of how to use the provisioner are
-available below this section.
-
-* `cookbooks_path` (string or array) - A list of paths to where cookbooks
-  are stored. By default this is "cookbooks", expecting a cookbooks folder
-  relative to the Vagrantfile location.
-
-* `data_bags_path` (string or array) - A path where data bags are stored. By
-  default, no data bag path is set. Chef 12 or higher is required to use the
-  array option. Chef 11 and lower only accept a string value.
-
-* `environments_path` (string) - A path where environment definitions are
-  located. By default, no environments folder is set.
-
-* `nodes_path` (string or array) - A list of paths where node objects
-  (in JSON format) are stored. By default, no nodes path is set. This value is
-  required.
-
-* `environment` (string) - The environment you want the Chef run to be
-  a part of. This requires Chef 11.6.0 or later, and that `environments_path`
-  is set.
-
-* `roles_path` (string or array) - A list of paths where roles are defined.
-  By default this is empty. Multiple role directories are only supported by
-  Chef 11.8.0 and later.
-
-* `synced_folder_type` (string) - The type of synced folders to use when
-  sharing the data required for the provisioner to work properly. By default
-  this will use the default synced folder type. For example, you can set this
-  to "nfs" to use NFS synced folders.
-
-
-In addition to all the options listed above, the Chef Zero provisioner supports
-the [common options for all Chef provisioners](/docs/provisioning/chef_common.html).
-
-## Usage
-
-The Chef Zero provisioner is configured basically the same way as the Chef Solo
-provisioner. See the [Chef Solo documentations](/docs/provisioning/chef_solo.html)
-for more information.
-
-A basic example could look like this:
-
-```ruby
-Vagrant.configure("2") do |config|
-  config.vm.provision "chef_zero" do |chef|
-    # Specify the local paths where Chef data is stored
-    chef.cookbooks_path = "cookbooks"
-    chef.data_bags_path = "data_bags"
-    chef.nodes_path = "nodes"
-    chef.roles_path = "roles"
-
-    # Add a recipe
-    chef.add_recipe "apache"
-
-    # Or maybe a role
-    chef.add_role "web"
-  end
-end
-```