vagrant-aws-mkubenka 0.7.2.pre.22 → 0.7.2.pre.24

data/vendor/bundle/ruby/2.7.0/bundler/gems/vagrant-22795b161bf6/website/pages/docs/providers/hyperv/index.mdx

@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: Hyper-V Provider
+sidebar_title: Hyper-V
+description: |-
+  Vagrant comes with support out of the box for Hyper-V, a native hypervisor
+  written by Microsoft. Hyper-V is available by default for almost all
+  Windows 8.1 and later installs.
+---
+
+# Hyper-V
+
+Vagrant comes with support out of the box for [Hyper-V](https://en.wikipedia.org/wiki/Hyper-V),
+a native hypervisor written by Microsoft. Hyper-V is available by default for
+almost all Windows 8.1 and later installs.
+
+The Hyper-V provider is compatible with Windows 8.1 and later only. Prior versions
+of Hyper-V do not include the necessary APIs for Vagrant to work.
+
+Hyper-V must be enabled prior to using the provider. Most Windows installations
+will not have Hyper-V enabled by default. Hyper-V is available by default for
+almost all Windows Enterprise, Professional, or Education 8.1 and later installs.
+To enable Hyper-V, go to "Programs and Features", click on "Turn Windows
+features on or off" and check the box next to "Hyper-V". Or install via
+PowerShell with:
+
+```powershell
+Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All
+```
+
+See official documentation [here](https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/quick-start/enable-hyper-v).
+
+~> **Warning:** Enabling Hyper-V will cause VirtualBox, VMware,
+and any other virtualization technology to no longer work. See
+[this blog post](http://www.hanselman.com/blog/SwitchEasilyBetweenVirtualBoxAndHyperVWithABCDEditBootEntryInWindows81.aspx)
+for an easy way to create a boot entry to boot Windows without Hyper-V enabled, if
+there will be times you will need other hypervisors.

data/vendor/bundle/ruby/2.7.0/bundler/gems/vagrant-22795b161bf6/website/pages/docs/providers/hyperv/limitations.mdx

@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: Limitations - Hyper-V Provider
+sidebar_title: Limitations
+description: |-
+  The Hyper-V provider works in almost every way like the VirtualBox
+  or VMware provider would, but has some limitations that are inherent to
+  Hyper-V itself.
+---
+
+# Limitations
+
+The Vagrant Hyper-V provider works in almost every way like the VirtualBox
+or VMware provider would, but has some limitations that are inherent to
+Hyper-V itself.
+
+## Limited Networking
+
+Vagrant does not yet know how to create and configure new networks for
+Hyper-V. When launching a machine with Hyper-V, Vagrant will prompt you
+asking what virtual switch you want to connect the virtual machine to.
+
+A result of this is that networking configurations in the Vagrantfile
+are completely ignored with Hyper-V. Vagrant cannot enforce a static IP
+or automatically configure a NAT.
+
+However, the IP address of the machine will be reported as part of
+the `vagrant up`, and you can use that IP address as if it were
+a host only network.
+
+## Snapshots
+
+Restoring snapshot VMs using `vagrant snapshot pop` or
+`vagrant snapshot restore` will sometimes raise errors when mounting
+SMB shared folders, however these mounts will still work inside the guest.

data/vendor/bundle/ruby/2.7.0/bundler/gems/vagrant-22795b161bf6/website/pages/docs/providers/hyperv/usage.mdx

@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: Usage - Hyper-V Provider
+sidebar_title: Usage
+description: |-
+  The Hyper-V provider is used just like any other provider. Please read the
+  general basic usage page for providers.
+---
+
+# Usage
+
+The Vagrant Hyper-V provider is used just like any other provider. Please
+read the general [basic usage](/docs/providers/basic_usage) page for
+providers.
+
+The value to use for the `--provider` flag is `hyperv`.
+
+Hyper-V also requires that you execute Vagrant with administrative
+privileges. Creating and managing virtual machines with Hyper-V requires
+admin rights. Vagrant will show you an error if it does not have the proper
+permissions.
+
+Boxes for Hyper-V can be easily found on
+[HashiCorp's Vagrant Cloud](https://vagrantcloud.com/boxes/search). To get started, you might
+want to try the `hashicorp/bionic64` box.

data/vendor/bundle/ruby/2.7.0/bundler/gems/vagrant-22795b161bf6/website/pages/docs/providers/index.mdx

@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: Providers
+sidebar_title: Providers
+description: |-
+  While Vagrant ships out of the box with support for VirtualBox, Hyper-V, and
+  Docker. Vagrant has the ability to manage other types of machines as well.
+  This is done by using other providers with Vagrant.
+---
+
+# Providers
+
+While Vagrant ships out of the box with support for [VirtualBox](https://www.virtualbox.org),
+[Hyper-V](https://www.microsoft.com/hyper-v), and [Docker](https://www.docker.io),
+Vagrant has the ability to manage other types of machines as well. This is done
+by using other _providers_ with Vagrant.
+
+Alternate providers can offer different features that make more sense in your use case.
+For example, if you are using Vagrant for any real work, [VMware](https://www.vmware.com)
+providers are recommended since they're well supported and generally more
+stable and performant than VirtualBox.
+
+Before you can use another provider, you must install it. Installation of other providers
+is done via the Vagrant plugin system.
+
+Once the provider is installed, usage is straightforward and simple, as
+you would expect with Vagrant. Read into the relevant subsections found in
+the navigation to the left for more information.

data/vendor/bundle/ruby/2.7.0/bundler/gems/vagrant-22795b161bf6/website/pages/docs/providers/installation.mdx

@@ -0,0 +1,16 @@
+---
+layout: docs
+page_title: Installation - Providers
+sidebar_title: Installation
+description: |-
+  Providers are distributed as Vagrant plugins, and are therefore installed
+  using standard plugin installation steps. After installing a plugin which
+  contains a provider, the provider should immediately be available.
+---
+
+# Provider Installation
+
+Providers are distributed as Vagrant plugins, and are therefore installed
+using [standard plugin installation steps](/docs/plugins/usage). After
+installing a plugin which contains a provider, the provider should
+immediately be available.

data/vendor/bundle/ruby/2.7.0/bundler/gems/vagrant-22795b161bf6/website/pages/docs/providers/virtualbox/boxes.mdx

@@ -0,0 +1,163 @@
+---
+layout: docs
+page_title: Creating a Base Box - VirtualBox Provider
+sidebar_title: Creating a Base Box
+description: |-
+  As with every Vagrant provider, the Vagrant VirtualBox provider has a custom
+  box format that affects how base boxes are made.
+---
+
+# Creating a Base Box
+
+As with [every Vagrant provider](/docs/providers/basic_usage), the
+Vagrant VirtualBox provider has a custom box format that affects how base
+boxes are made.
+
+Prior to reading this, you should read the
+[general guide to creating base boxes](/docs/boxes/base). Actually,
+it would probably be most useful to keep this open in a separate tab
+as you may be referencing it frequently while creating a base box. That
+page contains important information about common software to install
+on the box.
+
+Additionally, it is helpful to understand the
+[basics of the box file format](/docs/boxes/format).
+
+~> **Advanced topic!** This is a reasonably advanced topic that
+a beginning user of Vagrant does not need to understand. If you are
+just getting started with Vagrant, skip this and use an available
+box. If you are an experienced user of Vagrant and want to create
+your own custom boxes, this is for you.
+
+## Virtual Machine
+
+The virtual machine created in VirtualBox can use any configuration you would
+like, but Vagrant has some hard requirements:
+
+- The first network interface (adapter 1) _must_ be a NAT adapter.
+  Vagrant uses this to connect the first time.
+
+- The MAC address of the first network interface (the NAT adapter)
+  should be noted, since you will need to put it in a Vagrantfile
+  later as the value for `config.vm.base_mac`. To get this value, use
+  the VirtualBox GUI.
+
+Other than the above, you are free to customize the base virtual machine
+as you see fit.
+
+## Additional Software
+
+In addition to the software that should be installed based on the
+[general guide to creating base boxes](/docs/boxes/base),
+VirtualBox base boxes require some additional software.
+
+### VirtualBox Guest Additions
+
+[VirtualBox Guest Additions](https://www.virtualbox.org/manual/ch04.html)
+must be installed so that things such as shared folders can function.
+Installing guest additions also usually improves performance since the guest
+OS can make some optimizations by knowing it is running within VirtualBox.
+
+Before installing the guest additions, you will need the linux kernel headers
+and the basic developer tools. On Ubuntu, you can easily install these like
+so:
+
+```shell-session
+$ sudo apt-get install linux-headers-$(uname -r) build-essential dkms
+```
+
+#### To install via the GUI:
+
+Next, make sure that the guest additions image is available by using the
+GUI and clicking on "Devices" followed by "Install Guest Additions".
+Then mount the CD-ROM to some location. On Ubuntu, this usually looks like
+this:
+
+```shell-session
+$ sudo mount /dev/cdrom /media/cdrom
+```
+
+Finally, run the shell script that matches your system to install the
+guest additions. For example, for Linux on x86, it is the following:
+
+```shell-session
+$ sudo sh /media/cdrom/VBoxLinuxAdditions.run
+```
+
+If the command succeeds, then the guest additions are now installed!
+
+#### To install via the command line:
+
+You can find the appropriate guest additions version to match your VirtualBox
+version by selecting the appropriate version
+[here](http://download.virtualbox.org/virtualbox/). The examples below use
+4.3.8, which was the latest VirtualBox version at the time of writing.
+
+```text
+wget http://download.virtualbox.org/virtualbox/4.3.8/VBoxGuestAdditions_4.3.8.iso
+sudo mkdir /media/VBoxGuestAdditions
+sudo mount -o loop,ro VBoxGuestAdditions_4.3.8.iso /media/VBoxGuestAdditions
+sudo sh /media/VBoxGuestAdditions/VBoxLinuxAdditions.run
+rm VBoxGuestAdditions_4.3.8.iso
+sudo umount /media/VBoxGuestAdditions
+sudo rmdir /media/VBoxGuestAdditions
+```
+
+If you did not install a Desktop environment when you installed the operating
+system, as recommended to reduce size, the install of the VirtualBox additions
+should warn you about the lack of OpenGL or Window System Drivers, but you can
+safely ignore this.
+
+If the commands succeed, then the guest additions are now installed!
+
+## Packaging the Box
+
+Vagrant includes a simple way to package VirtualBox base boxes. Once you've
+installed all the software you want to install, you can run this command:
+
+```shell-session
+$ vagrant package --base my-virtual-machine
+```
+
+Where "my-virtual-machine" is replaced by the name of the virtual machine
+in VirtualBox to package as a base box.
+
+It will take a few minutes, but after it is complete, a file "package.box"
+should be in your working directory which is the new base box. At this
+point, you've successfully created a base box!
+
+## Raw Contents
+
+This section documents the actual raw contents of the box file. This is not
+as useful when creating a base box but can be useful in debugging issues
+if necessary.
+
+A VirtualBox base box is an archive of the resulting files of
+[exporting](https://www.virtualbox.org/manual/ch08.html#vboxmanage-export)
+a VirtualBox virtual machine. Here is an example of what is contained
+in such a box:
+
+```shell-session
+$ tree
+.
+|-- Vagrantfile
+|-- box-disk1.vmdk
+|-- box.ovf
+|-- metadata.json
+
+0 directories, 4 files
+```
+
+In addition to the files from exporting a VirtualBox VM, there is
+the "metadata.json" file used by Vagrant itself.
+
+Also, there is a "Vagrantfile." This contains some configuration to
+properly set the MAC address of the NAT network device, since VirtualBox
+requires this to be correct in order to function properly. If you are
+not using `vagrant package --base` above, you will have to set the
+`config.vm.base_mac` setting in this Vagrantfile to the MAC address
+of the NAT device without colons.
+
+When bringing up a VirtualBox backed machine, Vagrant
+[imports](https://www.virtualbox.org/manual/ch08.html#vboxmanage-import)
+the "box.ovf" file found in the box contents.

data/vendor/bundle/ruby/2.7.0/bundler/gems/vagrant-22795b161bf6/website/pages/docs/providers/virtualbox/common-issues.mdx

@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: Common Issues - VirtualBox Provider
+sidebar_title: Common Issues
+description: |-
+  This page lists some common issues people run into with Vagrant and VirtualBox
+  as well as solutions for those issues.
+---
+
+# Common Issues
+
+This page lists some common issues people run into with Vagrant and VirtualBox
+as well as solutions for those issues.
+
+## Hanging on Windows
+
+If Vagrant commands are hanging on Windows because they're communicating
+to VirtualBox, this may be caused by a permissions issue with VirtualBox.
+This is easy to fix. Starting VirtualBox as a normal user or as an
+administrator will prevent you from using it in the opposite way. Please keep
+in mind that when Vagrant interacts with VirtualBox, it will interact with
+it with the same access level as the console running Vagrant.
+
+To fix this issue, completely shut down all VirtualBox machines and GUIs.
+Wait a few seconds. Then, launch VirtualBox only with the access level you
+wish to use.
+
+## DNS Not Working
+
+If DNS is not working within your VM, then you may need to enable
+a DNS proxy (built-in to VirtualBox). Please [see the StackOverflow answers
+here](https://serverfault.com/questions/453185/vagrant-virtualbox-dns-10-0-2-3-not-working)
+for a guide on how to do that.

data/vendor/bundle/ruby/2.7.0/bundler/gems/vagrant-22795b161bf6/website/pages/docs/providers/virtualbox/configuration.mdx

@@ -0,0 +1,137 @@
+---
+layout: docs
+page_title: Configuration - VirtualBox Provider
+sidebar_title: Configuration
+description: |-
+  The VirtualBox provider exposes some additional configuration options
+  that allow you to more finely control your VirtualBox-powered Vagrant
+  environments.
+---
+
+# Configuration
+
+The VirtualBox provider exposes some additional configuration options
+that allow you to more finely control your VirtualBox-powered Vagrant
+environments.
+
+## GUI vs. Headless
+
+By default, VirtualBox machines are started in headless mode, meaning
+there is no UI for the machines visible on the host machine. Sometimes,
+you want to have a UI. Common use cases include wanting to see a browser
+that may be running in the machine, or debugging a strange boot issue.
+You can easily tell the VirtualBox provider to boot with a GUI:
+
+```ruby
+config.vm.provider "virtualbox" do |v|
+  v.gui = true
+end
+```
+
+## Virtual Machine Name
+
+You can customize the name that appears in the VirtualBox GUI by
+setting the `name` property. By default, Vagrant sets it to the containing
+folder of the Vagrantfile plus a timestamp of when the machine was created.
+By setting another name, your VM can be more easily identified.
+
+```ruby
+config.vm.provider "virtualbox" do |v|
+  v.name = "my_vm"
+end
+```
+
+## Default NIC Type
+
+By default Vagrant will not set the NIC type for network interfaces. This
+allows VirtualBox to apply the default NIC type for the guest. If you would
+like to use a specific NIC type by default for guests, set the `default_nic_type`
+option:
+
+```ruby
+config.vm.provider "virtualbox" do |v|
+  v.default_nic_type = "82543GC"
+end
+```
+
+## Linked Clones
+
+By default new machines are created by importing the base box. For large
+boxes this produces a large overhead in terms of time (the import operation)
+and space (the new machine contains a copy of the base box's image).
+Using linked clones can drastically reduce this overhead.
+
+Linked clones are based on a master VM, which is generated by importing the
+base box only once the first time it is required. For the linked clones only
+differencing disk images are created where the parent disk image belongs to
+the master VM.
+
+```ruby
+config.vm.provider "virtualbox" do |v|
+  v.linked_clone = true
+end
+```
+
+To have backward compatibility:
+
+```ruby
+config.vm.provider "virtualbox" do |v|
+  v.linked_clone = true if Gem::Version.new(Vagrant::VERSION) >= Gem::Version.new('1.8.0')
+end
+```
+
+If you do not want backward compatibility and want to force users to
+support linked cloning, you can use `Vagrant.require_version` with 1.8.
+
+-> **Note:** the generated master VMs are currently not removed
+automatically by Vagrant. This has to be done manually. However, a master
+VM can only be removed when there are no linked clones connected to it.
+
+## Checking for Guest Additions
+
+By default Vagrant will check for the [VirtualBox Guest
+Additions](https://www.virtualbox.org/manual/ch04.html) when starting a
+machine, and will output a warning if the guest additions are missing or
+out-of-date. You can skip the guest additions check by setting the
+`check_guest_additions` option:
+
+```ruby
+config.vm.provider "virtualbox" do |v|
+  v.check_guest_additions = false
+end
+```
+
+## VBoxManage Customizations
+
+[VBoxManage](https://www.virtualbox.org/manual/ch08.html) is a utility that can
+be used to make modifications to VirtualBox virtual machines from the command
+line.
+
+Vagrant exposes a way to call any command against VBoxManage just prior
+to booting the machine:
+
+```ruby
+config.vm.provider "virtualbox" do |v|
+  v.customize ["modifyvm", :id, "--cpuexecutioncap", "50"]
+end
+```
+
+In the example above, the VM is modified to have a host CPU execution
+cap of 50%, meaning that no matter how much CPU is used in the VM, no
+more than 50% would be used on your own host machine. Some details:
+
+- The `:id` special parameter is replaced with the ID of the virtual
+  machine being created, so when a VBoxManage command requires an ID, you
+  can pass this special parameter.
+
+- Multiple `customize` directives can be used. They will be executed in the
+  order given.
+
+There are some convenience shortcuts for memory and CPU settings:
+
+```ruby
+config.vm.provider "virtualbox" do |v|
+  v.memory = 1024
+  v.cpus = 2
+end
+```