tamtam-vagrant-reload 1.1.2 → 1.2.1

data/vendor/cache/vagrant-2092df529ae7/website/content/docs/vagrantfile/machine_settings.mdx

@@ -0,0 +1,165 @@
+---
+layout: docs
+page_title: config.vm - Vagrantfile
+description: |-
+  The settings within "config.vm" modify the configuration of the
+  machine that Vagrant manages.
+---
+
+# Machine Settings
+
+**Config namespace: `config.vm`**
+
+The settings within `config.vm` modify the configuration of the
+machine that Vagrant manages.
+
+## Available Settings
+
+- `config.vm.allow_fstab_modification` (boolean) - If true, will add fstab
+  entries for synced folders. If false, no modifications to fstab will be made
+  by Vagrant. Note, this may mean that folders will not be automatically mounted
+  on machine reboot. Defaults to true.
+
+- `config.vm.allow_hosts_modification` (boolean) - If false, will prevent Vagrant
+  from writing to `/etc/hosts`. Defaults to true.
+
+- `config.vm.allowed_synced_folder_types` (array of strings) - A list of allowed
+synced folder plugins. This will restrict plugin selection when Vagrant is
+determining the default synced folder type. The elements of the array should be
+the name of the synced folder plugin.
+
+- `config.vm.base_mac` (string) - The MAC address to be assigned to the default
+  NAT interface on the guest. _Support for this option is provider dependent._
+
+- `config.vm.base_address` (string) - The IP address to be assigned to the default
+  NAT interface on the guest. _Support for this option is provider dependent._
+
+- `config.vm.boot_timeout` (integer) - The time in seconds that Vagrant will wait
+  for the machine to boot and be accessible. By default this is 300 seconds.
+
+- `config.vm.box` (string) - This configures what [box](/vagrant/docs/boxes) the
+  machine will be brought up against. The value here should be the name
+  of an installed box or a shorthand name of a box in
+  [HashiCorp's Vagrant Cloud](/vagrant/vagrant-cloud).
+
+- `config.vm.box_check_update` (boolean) - If true, Vagrant will check for updates to
+  the configured box on every `vagrant up`. If an update is found, Vagrant
+  will tell the user. By default this is true. Updates will only be checked
+  for boxes that properly support updates (boxes from
+  [HashiCorp's Vagrant Cloud](/vagrant/vagrant-cloud)
+  or some other versioned box).
+
+- `config.vm.box_download_checksum` (string) - The checksum of the box specified by
+  `config.vm.box_url`. If not specified, no checksum comparison will be done.
+  If specified, Vagrant will compare the checksum of the downloaded box to
+  this value and error if they do not match. Checksum checking is only done
+  when Vagrant must download the box. If this is specified, then
+  `config.vm.box_download_checksum_type` must also be specified.
+
+- `config.vm.box_download_checksum_type` (string) - The type of checksum specified
+  by `config.vm.box_download_checksum` (if any). Supported values are
+  currently "md5", "sha1", "sha256", "sha384", and "sha512".
+
+- `config.vm.box_download_client_cert` (string) - Path to a client certificate to
+  use when downloading the box, if it is necessary. By default, no client
+  certificate is used to download the box.
+
+- `config.vm.box_download_ca_cert` (string) - Path to a CA cert bundle to use when
+  downloading a box directly. By default, Vagrant will use the Mozilla CA cert
+  bundle.
+
+- `config.vm.box_download_ca_path` (string) - Path to a directory containing
+  CA certificates for downloading a box directly. By default, Vagrant will
+  use the Mozilla CA cert bundle.
+
+- `config.vm.box_download_options` (map) - A map of extra download options
+  to pass to the downloader. For example, a path to a key that the downloader
+  should use could be specified as `{key: "<path/to/key>"}`. The keys should
+  be options supported by `curl` using the unshortened form of the flag. For
+  example, use `append` instead of `a`. To pass a curl option that does not
+  accept a value, include the option in the map with the value `true`. For
+  example specify the `--fail` flag as `{fail: true}`.
+
+- `config.vm.box_download_insecure` (boolean) - If true, then SSL certificates
+  from the server will not be verified. By default, if the URL is an HTTPS
+  URL, then SSL certs will be verified.
+
+- `config.vm.box_download_location_trusted` (boolean) - If true, then all HTTP redirects will be
+  treated as trusted. That means credentials used for initial URL will be used for
+  all subsequent redirects. By default, redirect locations are untrusted so credentials
+  (if specified) used only for initial HTTP request.
+
+- `config.vm.box_url` (string, array of strings) - The URL that the configured box can be found at.
+  If `config.vm.box` is a shorthand to a box in [HashiCorp's Vagrant Cloud](/vagrant/vagrant-cloud)
+  then this value does not need to be specified. Otherwise, it should
+  point to the proper place where the box can be found if it is not
+  installed. This can also be an array of multiple URLs. The URLs will be tried in
+  order.
+
+  Note that any client certificates, insecure download settings, and
+  so on will apply to all URLs in this list. The URLs can also be local files
+  by using the `file://` scheme. For example: `file://tmp/test.box`.
+
+- `config.vm.box_version` (string) - The version of the box to use. This defaults to
+  ">= 0" (the latest version available). This can contain an arbitrary list
+  of constraints, separated by commas, such as: `>= 1.0, < 1.5`. When constraints
+  are given, Vagrant will use the latest available box satisfying these
+  constraints.
+
+- `config.vm.cloud_init` - Stores various [cloud_init](/vagrant/docs/cloud-init) configurations
+  on the machine. **Currently experimental!** Read the documentation for more
+  information on how to enable this feature.
+
+- `config.vm.communicator` (string) - The communicator type to use to connect to the
+  guest box. By default this is `"ssh"`, but should be changed to `"winrm"` for
+  Windows guests.
+
+- `config.vm.disk` - Stores various virtual [disk](/vagrant/docs/disks) configurations
+  on the machine. **Currently experimental!** Read the documentation for more
+  information on how to enable this feature.
+
+- `config.vm.graceful_halt_timeout` (integer) - The time in seconds that Vagrant will
+  wait for the machine to gracefully halt when `vagrant halt` is called.
+  Defaults to 60 seconds.
+
+- `config.vm.guest` (string, symbol) - The guest OS that will be running within this
+  machine. This defaults to `:linux`, and Vagrant will auto-detect the
+  proper distro. However, this should be changed to `:windows` for Windows guests.
+  Vagrant needs to know this information to perform some guest OS-specific things
+  such as mounting folders and configuring networks.
+
+- `config.vm.hostname` (string) - The hostname the machine should have. Defaults
+  to nil. If nil, Vagrant will not manage the hostname. If set to a string,
+  the hostname will be set on boot. If set, Vagrant will update `/etc/hosts`
+  on the guest with the configured hostname.
+
+- `config.vm.ignore_box_vagrantfile` (boolean) - If true, Vagrant will not load the the
+  settings found inside a boxes Vagrantfile, if present. Defaults to `false`.
+
+- `config.vm.network` - Configures [networks](/vagrant/docs/networking/) on
+  the machine. Please see the networking page for more information.
+
+- `config.vm.post_up_message` (string) - A message to show after `vagrant up`. This
+  will be shown to the user and is useful for containing instructions
+  such as how to access various components of the development environment.
+
+- `config.vm.provider` - Configures [provider-specific configuration](/vagrant/docs/providers/configuration),
+  which is used to modify settings which are specific to a certain
+  [provider](/vagrant/docs/providers/). If the provider you are configuring
+  does not exist or is not setup on the system of the person who runs
+  `vagrant up`, Vagrant will ignore this configuration block. This allows
+  a Vagrantfile that is configured for many providers to be shared among
+  a group of people who may not have all the same providers installed.
+
+- `config.vm.provision` - Configures [provisioners](/vagrant/docs/provisioning/)
+  on the machine, so that software can be automatically installed and configured
+  when the machine is created. Please see the page on provisioners for more
+  information on how this setting works.
+
+- `config.vm.synced_folder` - Configures [synced folders](/vagrant/docs/synced-folders/)
+  on the machine, so that folders on your host machine can be synced to
+  and from the guest machine. Please see the page on synced folders for
+  more information on how this setting works.
+
+- `config.vm.usable_port_range` (range) - A range of ports Vagrant can use for
+  handling port collisions and such. Defaults to `2200..2250`.

data/vendor/cache/vagrant-2092df529ae7/website/content/docs/vagrantfile/ssh_settings.mdx

@@ -0,0 +1,147 @@
+---
+layout: docs
+page_title: config.ssh - Vagrantfile
+description: |-
+  The settings within "config.ssh" relate to configuring how Vagrant
+  will access your machine over SSH. As with most Vagrant settings, the
+  defaults are typically fine, but you can fine tune whatever you would like.
+---
+
+# SSH Settings
+
+**Config namespace: `config.ssh`**
+
+The settings within `config.ssh` relate to configuring how Vagrant
+will access your machine over SSH. As with most Vagrant settings, the
+defaults are typically fine, but you can fine tune whatever you would like.
+
+## Available Settings
+
+- `config.ssh.compression` (boolean) - If `false`, this setting will not include the
+  compression setting when ssh'ing into a machine. If this is not set, it will
+  default to `true` and `Compression=yes` will be enabled with ssh.
+
+- `config.ssh.connect_timeout` (integer) - Number of seconds to wait for establishing
+  an SSH connection to the guest. Defaults to `15`.
+
+- `config.ssh.config` (string) - Path to a custom ssh_config file to use for configuring
+  the SSH connections.
+
+- `config.ssh.dsa_authentication` (boolean) - If `false`, this setting will not include
+  `DSAAuthentication` when ssh'ing into a machine. If this is not set, it will
+  default to `true` and `DSAAuthentication=yes` will be used with ssh.
+
+- `config.ssh.export_command_template` (string) - The template used to generate
+  exported environment variables in the active session. This can be useful
+  when using a Bourne incompatible shell like C shell. The template supports
+  two variables which are replaced with the desired environment variable key and
+  environment variable value: `%ENV_KEY%` and `%ENV_VALUE%`. The default template
+  is:
+
+  ```ruby
+  config.ssh.export_command_template = 'export %ENV_KEY%="%ENV_VALUE%"'
+  ```
+
+- `config.ssh.extra_args` (array of strings) - This settings value is passed directly
+  into the ssh executable. This allows you to pass any arbitrary commands to do things such
+  as reverse tunneling down into the SSH program. These options can either be
+  single flags set as strings such as `"-6"` for IPV6 or an array of arguments
+  such as `["-L", "8008:localhost:80"]` for enabling a tunnel from host port 8008
+  to port 80 on guest. **Note:** This option only affects the `ssh` command or instances
+  where the SSH executable is invoked (non-interactive SSH connections use the internal
+  SSH communicator which is unaffected by this setting).
+
+- `config.ssh.forward_agent` (boolean) - If `true`, agent forwarding over SSH
+  connections is enabled. Defaults to false.
+
+- `config.ssh.forward_env` (array of strings) - An array of host environment variables to
+  forward to the guest. If you are familiar with OpenSSH, this corresponds to the `SendEnv`
+  parameter.
+
+  ```ruby
+  config.ssh.forward_env = ["CUSTOM_VAR"]
+  ```
+
+- `config.ssh.forward_x11` (boolean) - If `true`, X11 forwarding over SSH connections
+  is enabled. Defaults to false.
+
+- `config.ssh.guest_port` (integer) - The port on the guest that SSH is running on. This
+  is used by some providers to detect forwarded ports for SSH. For example, if
+  this is set to 22 (the default), and Vagrant detects a forwarded port to
+  port 22 on the guest from port 4567 on the host, Vagrant will attempt
+  to use port 4567 to talk to the guest if there is no other option.
+
+- `config.ssh.host` (string) - The hostname or IP to SSH into. By default this is
+  empty, because the provider usually figures this out for you.
+
+- `config.ssh.insert_key` (boolean) - By default or if set to `true`, Vagrant will automatically insert
+  a keypair to use for SSH, replacing Vagrant's default insecure key inside the machine
+  if detected. If you already use private keys for authentication to your guest, or are relying
+  on the default insecure key, this option will not be used. If set to `false`,
+  Vagrant will not automatically add a keypair to the guest.
+
+- `config.ssh.keep_alive` (boolean) - If `true`, this setting SSH will send keep-alive packets
+  every 5 seconds by default to keep connections alive.
+
+- `config.ssh.keys_only` (boolean) - Only use Vagrant-provided SSH private keys (do not use
+  any keys stored in ssh-agent). The default value is `true`.
+
+- `config.ssh.paranoid` (boolean) - Perform strict host-key verification. The default value is
+  `false`.
+
+  !> **Deprecation:** The `config.ssh.paranoid` option is deprecated and will be removed
+  in a future release. Please use the `config.ssh.verify_host_key` option instead.
+
+- `config.ssh.password` (string) - This sets a password that Vagrant will use to
+  authenticate the SSH user. Note that Vagrant recommends you use key-based
+  authentication rather than a password (see `private_key_path`) below. If
+  you use a password, Vagrant will automatically insert a keypair if
+  `insert_key` is true.
+
+- `config.ssh.port` (integer) - The port to SSH into. By default this is port 22.
+
+- `config.ssh.private_key_path` (string, array of strings) - The path to the private
+  key to use to SSH into the guest machine. By default this is the insecure private key
+  that ships with Vagrant, since that is what public boxes use. If you make
+  your own custom box with a custom SSH key, this should point to that
+  private key. You can also specify multiple private keys by setting this to be an array.
+  This is useful, for example, if you use the default private key to bootstrap
+  the machine, but replace it with perhaps a more secure key later.
+
+- `config.ssh.proxy_command` (string) - A command-line command to execute that receives
+  the data to send to SSH on stdin. This can be used to proxy the SSH connection.
+  `%h` in the command is replaced with the host and `%p` is replaced with
+  the port.
+
+- `config.ssh.pty` (boolean) - If `true`, pty will be used for provisioning. Defaults to false.
+
+  This setting is an _advanced feature_ that should not be enabled unless
+  absolutely necessary. It breaks some other features of Vagrant, and is
+  really only exposed for cases where it is absolutely necessary. If you can find
+  a way to not use a pty, that is recommended instead.
+
+  When pty is enabled, it is important to note that command output will _not_ be
+  streamed to the UI. Instead, the output will be delivered in full to the UI
+  once the command has completed.
+
+- `config.ssh.remote_user` (string) - The "remote user" value used to replace the `%r`
+  character(s) used within a configured `ProxyCommand`. This value is only used by the
+  net-ssh library (ignored by the `ssh` executable) and should not be used in general.
+  This defaults to the value of `config.ssh.username`.
+
+- `config.ssh.shell` (string) - The shell to use when executing SSH commands from
+  Vagrant. By default this is `bash -l`.
+
+- `config.ssh.sudo_command` (string) - The command to use when executing a command
+  with `sudo`. This defaults to `sudo -E -H %c`. The `%c` will be replaced by
+  the command that is being executed.
+
+- `config.ssh.username` (string) - This sets the username that Vagrant will SSH
+  as by default. Providers are free to override this if they detect a more
+  appropriate user. By default this is "vagrant", since that is what most
+  public boxes are made as.
+
+- `config.ssh.verify_host_key` (string, symbol) - Perform strict host-key verification. The
+  default value is `:never`. The other options are `:accept_new_or_local_tunnel`,
+  `:accept_new`, or `:always`, which each refer to one of
+  [net-ssh](https://net-ssh.github.io/net-ssh/)'s `Net::SSH::Verifiers` subclasses.

data/vendor/cache/vagrant-2092df529ae7/website/content/docs/vagrantfile/tips.mdx

@@ -0,0 +1,71 @@
+---
+layout: docs
+page_title: Tips & Tricks - Vagrantfile
+description: |-
+  The Vagrantfile is a very flexible configuration format. Since it is just
+  Ruby, there is a lot you can do with it. However, in that same vein, since
+  it is Ruby, there are a lot of ways you can shoot yourself in the foot. When
+  using some of the tips and tricks on this page, please take care to use them
+  correctly.
+---
+
+# Tips & Tricks
+
+The Vagrantfile is a very flexible configuration format. Since it is just
+Ruby, there is a lot you can do with it. However, in that same vein, since
+it is Ruby, there are a lot of ways you can shoot yourself in the foot. When
+using some of the tips and tricks on this page, please take care to use them
+correctly.
+
+## Loop Over VM Definitions
+
+If you want to apply a slightly different configuration to many
+multi-machine machines, you can use a loop to do this. For example, if
+you wanted to create three machines:
+
+```ruby
+(1..3).each do |i|
+  config.vm.define "node-#{i}" do |node|
+    node.vm.provision "shell",
+      inline: "echo hello from node #{i}"
+  end
+end
+```
+
+~> **Warning:** The inner portion of multi-machine definitions
+and provider overrides are lazy-loaded. This can cause issues if you change
+the value of a variable used within the configs. For example, the loop below
+_does not work_:
+
+```ruby
+# THIS DOES NOT WORK!
+for i in 1..3 do
+  config.vm.define "node-#{i}" do |node|
+    node.vm.provision "shell",
+      inline: "echo hello from node #{i}"
+  end
+end
+```
+
+The `for i in ...` construct in Ruby actually modifies the value of `i`
+for each iteration, rather than making a copy. Therefore, when you run this,
+every node will actually provision with the same text.
+
+This is an easy mistake to make, and Vagrant cannot really protect against it,
+so the best we can do is mention it here.
+
+## Overwrite host locale in SSH session
+
+Usually, host locale environment variables are passed to guest. It may cause
+failures if the guest software do not support host locale. One possible solution
+is override locale in the `Vagrantfile`:
+
+```ruby
+ENV["LC_ALL"] = "en_US.UTF-8"
+
+Vagrant.configure("2") do |config|
+  # ...
+end
+```
+
+The change is only visible within the `Vagrantfile`.

data/vendor/cache/vagrant-2092df529ae7/website/content/docs/vagrantfile/vagrant_settings.mdx

@@ -0,0 +1,62 @@
+---
+layout: docs
+page_title: config.vagrant - Vagrantfile
+description: |-
+  The settings within "config.vagrant" modify the behavior of Vagrant
+  itself.
+---
+
+# Vagrant Settings
+
+**Config namespace: `config.vagrant`**
+
+The settings within `config.vagrant` modify the behavior of Vagrant
+itself.
+
+## Available Settings
+
+- `config.vagrant.host` (string, symbol) - This sets the type of host machine
+  that is running Vagrant. By default this is `:detect`, which causes Vagrant to
+  auto-detect the host. Vagrant needs to know this information in order to perform
+  some host-specific things, such as preparing NFS folders if they're enabled.
+  You should only manually set this if auto-detection fails.
+
+- `config.vagrant.plugins` - (string, array, hash) - Define plugin, list of
+  plugins, or definition of plugins to install for the local project. Vagrant
+  will require these plugins be installed and available for the project. If
+  the plugins are not available, it will attempt to automatically install
+  them into the local project. When requiring a single plugin, a string can
+  be provided:
+
+  ```ruby
+  config.vagrant.plugins = "vagrant-plugin"
+  ```
+
+  If multiple plugins are required, they can be provided as an array:
+
+  ```ruby
+  config.vagrant.plugins = ["vagrant-plugin", "vagrant-other-plugin"]
+  ```
+
+  Plugins can also be defined as a Hash, which supports setting extra options
+  for the plugins. When a Hash is used, the key is the name of the plugin, and
+  the value is a Hash of options for the plugin. For example, to set an explicit
+  version of a plugin to install:
+
+  ```ruby
+  config.vagrant.plugins = {"vagrant-scp" => {"version" => "1.0.0"}}
+  ```
+
+  Supported options are:
+
+  - `entry_point` - Path for Vagrant to load plugin
+  - `sources` - Custom sources for downloading plugin
+  - `version` - Version constraint for plugin
+
+- `config.vagrant.sensitive` - (string, array) - Value or list of values that
+  should not be displayed in Vagrant's output. Value(s) will be removed from
+  Vagrant's normal UI output as well as logger output.
+
+  ```ruby
+  config.vagrant.sensitive = ["MySecretPassword", ENV["MY_TOKEN"]]
+  ```

data/vendor/cache/vagrant-2092df529ae7/website/content/docs/vagrantfile/vagrant_version.mdx

@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: Minimum Vagrant Version - Vagrantfile
+description: |-
+  A set of Vagrant version requirements can be specified in the Vagrantfile
+  to enforce that people use a specific version of Vagrant with a Vagrantfile.
+  This can help with compatibility issues that may otherwise arise from using
+  a too old or too new Vagrant version with a Vagrantfile.
+---
+
+# Minimum Vagrant Version
+
+A set of Vagrant version requirements can be specified in the Vagrantfile
+to enforce that people use a specific version of Vagrant with a Vagrantfile.
+This can help with compatibility issues that may otherwise arise from using
+a too old or too new Vagrant version with a Vagrantfile.
+
+Vagrant version requirements should be specified at the top of a Vagrantfile
+with the `Vagrant.require_version` helper:
+
+```ruby
+Vagrant.require_version ">= 1.3.5"
+```
+
+In the case above, the Vagrantfile will only load if the version loading it
+is Vagrant 1.3.5 or greater.
+
+Multiple requirements can be specified as well:
+
+```ruby
+Vagrant.require_version ">= 1.3.5", "< 1.4.0"
+```

data/vendor/cache/vagrant-2092df529ae7/website/content/docs/vagrantfile/version.mdx

@@ -0,0 +1,59 @@
+---
+layout: docs
+page_title: Configuration Version - Vagrantfile
+description: |-
+  Configuration versions are the mechanism by which Vagrant 1.1+ is able to
+  remain backwards compatible with Vagrant 1.0.x Vagrantfiles, while introducing
+  dramatically new features and configuration options.
+---
+
+# Configuration Version
+
+Configuration versions are the mechanism by which Vagrant 1.1+ is able
+to remain [backwards compatible](/vagrant/docs/installation/backwards-compatibility)
+with Vagrant 1.0.x Vagrantfiles, while introducing dramatically new features
+and configuration options.
+
+If you run `vagrant init` today, the Vagrantfile will be in roughly the
+following format:
+
+```ruby
+Vagrant.configure("2") do |config|
+  # ...
+end
+```
+
+The `"2"` in the first line above represents the version of the configuration
+object `config` that will be used for configuration for that block (the
+section between the `do` and the `end`). This object can be very
+different from version to version.
+
+Currently, there are only two supported versions: "1" and "2". Version 1
+represents the configuration from Vagrant 1.0.x. "2" represents the configuration
+for 1.1+ leading up to 2.0.x.
+
+When loading Vagrantfiles, Vagrant uses the proper configuration object
+for each version, and properly merges them, just like any other configuration.
+
+The important thing to understand as a general user of Vagrant is that
+_within a single configuration section_, only a single version can be used.
+You cannot use the new `config.vm.provider` configurations in a version 1
+configuration section. Likewise, `config.vm.forward_port` will not work
+in a version 2 configuration section (it was renamed).
+
+If you want, you can mix and match multiple configuration versions in the
+same Vagrantfile. This is useful if you found some useful configuration
+snippet or something that you want to use. Example:
+
+```ruby
+Vagrant.configure("1") do |config|
+  # v1 configs...
+end
+
+Vagrant.configure("2") do |config|
+  # v2 configs...
+end
+```
+
+-> **What is `Vagrant::Config.run`?** You may see this in Vagrantfiles. This was actually how Vagrant 1.0.x
+did configuration. In Vagrant 1.1+, this is synonymous with `Vagrant.configure("1")`.

data/vendor/cache/vagrant-2092df529ae7/website/content/docs/vagrantfile/winrm_settings.mdx

@@ -0,0 +1,78 @@
+---
+layout: docs
+page_title: config.winrm - Vagrantfile
+description: |-
+  The settings within "config.winrm" relate to configuring how Vagrant
+  will access your Windows guest over WinRM. As with most Vagrant settings, the
+  defaults are typically fine, but you can fine tune whatever you would like.
+---
+
+# WinRM Settings
+
+**Config namespace: `config.winrm`**
+
+The settings within `config.winrm` relate to configuring how Vagrant
+will access your Windows guest over WinRM. As with most Vagrant settings, the
+defaults are typically fine, but you can fine tune whatever you would like.
+
+These settings are only used if you've set your communicator type to `:winrm`.
+
+## Available Settings
+
+- `config.winrm.username` (string) - This sets the username that Vagrant will use
+  to login to the WinRM web service by default. Providers are free to override
+  this if they detect a more appropriate user. By default this is "vagrant,"
+  since that is what most public boxes are made as.
+
+- `config.winrm.password` (string) - This sets a password that Vagrant will use to
+  authenticate the WinRM user. By default this is "vagrant," since that is
+  what most public boxes are made as.
+
+- `config.winrm.host` (string) - The hostname or IP to connect to the WinRM service.
+  By default this is empty, because the provider usually figures this out for
+  you.
+
+- `config.winrm.port` (integer) - The WinRM port to connect to, by default 5985. If ssl
+  is enabled, the default port is 5986.
+
+- `config.winrm.guest_port` (integer) - The port on the guest that WinRM is running on.
+  This is used by some providers to detect forwarded ports for WinRM. For
+  example, if this is set to 5985 (the default), and Vagrant detects a forwarded
+  port to port 5985 on the guest from port 4567 on the host, Vagrant will attempt
+  to use port 4567 to talk to the guest if there is no other option.
+
+- `config.winrm.transport` (symbol)- The transport used for WinRM communication.
+  Valid settings include: `:negotiate`, `:ssl`, and `:plaintext`. The default is `:negotiate`.
+
+- `config.winrm.basic_auth_only` (boolean) - Whether to use Basic Authentication. Defaults
+  to `false`. If set to `true` you should also use the `:plaintext` transport setting and
+  the Windows machine must be configured appropriately.
+
+  -> **Note:** It is strongly recommended that you only use basic authentication for
+  debugging purposes. Credentials will be transferred in plain text.
+
+- `config.winrm.execution_time_limit` (string) - The amount of time that is allowed to
+  complete task. This defaults to "PT2H", that is 2 hours.
+
+- `config.winrm.ssl_peer_verification` (boolean) - When set to `false` ssl certificate
+  validation is not performed. By default this is true.
+
+- `config.winrm.timeout` (integer) - The maximum amount of time to wait for a response
+  from the endpoint. This defaults to 1800 seconds. Note that this will not "timeout"
+  commands that exceed this amount of time to process, it just requires the endpoint to
+  report the status of the command before the given amount of time passes.
+
+- `config.winrm.max_tries` (integer) - The maximum number of times to retry opening
+  a shell after failure. This defaults to 20.
+
+- `config.winrm.retry_delay` (integer) - The amount of time to wait between retries and
+  defaults to 2 seconds.
+
+- `config.winrm.codepage` (string) - The WINRS_CODEPAGE which is the client's console
+  output code page. By default this is not set by Vagrant.
+
+  -> **Note:** Versions of Windows older than Windows 7/Server 2008 R2 may exhibit
+  undesirable behavior using the default UTF-8 codepage. When using these older
+  versions of Windows, its best to use the native code page of the server's locale.
+  For example, en-US servers will have a codepage of 437. The Windows `chcp` command
+  can be used to determine the value of the native codepage.