vagrant-packet 0.1.2 → 0.1.3

data/vendor/bundle/ruby/2.5.0/bundler/gems/vagrant-04f7215b5e3f/templates/locales/guest_windows.yml

@@ -1,23 +0,0 @@
-en:
-  vagrant_windows:
-    errors:
-      public_key_directory_failure: |-
-        Vagrant failed to properly discover the correct paths for the
-        temporary directory and user profile directory on the Windows
-        guest. Please ensure the guest is properly configured.
-      network_winrm_required: |-
-        Configuring networks on Windows requires the communicator to be
-        set to WinRM. To do this, add the following to your Vagrantfile:
-
-          config.vm.communicator = "winrm"
-
-        Note that the Windows guest must be configured to accept insecure
-        WinRM connections, and the WinRM port must be forwarded properly from
-        the guest machine. This is not always done by default.
-      rename_computer_failed: |-
-        Renaming the Windows guest failed. Most often this is because you've
-        specified a FQDN instead of just a host name.
-
-        Ensure the new guest name is properly formatted. Standard names may
-        contain letters (a-z, A-Z), numbers (0-9), and hyphens (-), but no
-        spaces or periods (.). The name may not consist entirely of digits.

data/vendor/bundle/ruby/2.5.0/bundler/gems/vagrant-04f7215b5e3f/templates/locales/providers_docker.yml

@@ -1,234 +0,0 @@
-en:
-  docker_provider:
-    already_built: |-
-      Image is already built from the Dockerfile. `vagrant reload` to rebuild.
-    build_image_destroy: |-
-      Removing built image...
-    build_image_destroy_in_use: |-
-      Build image couldn't be destroyed because the image is in use. The
-      image must be destroyed manually in the future if you want to remove
-      it.
-    build_image_invalid: |-
-      Build image no longer exists. Rebuilding...
-    building: |-
-      Building the container from a Dockerfile...
-    building_named_dockerfile: |-
-      Building the container from the named Dockerfile: %{file}...
-    creating: |-
-      Creating the container...
-    created: |-
-      Container created: %{id}
-    host_machine_disabling_folders: |-
-      Removing synced folders...
-    host_machine_forwarded_ports: |-
-      Warning: When using a remote Docker host, forwarded ports will NOT be
-      immediately available on your machine. They will still be forwarded on
-      the remote machine, however, so if you have a way to access the remote
-      machine, then you should be able to access those ports there. This is
-      not an error, it is only an informational message.
-    host_machine_needed: |-
-      Docker host is required. One will be created if necessary...
-    host_machine_ready: |-
-      Docker host VM is already ready.
-    host_machine_starting: |-
-      Vagrant will now create or start a local VM to act as the Docker
-      host. You'll see the output of the `vagrant up` for this VM below.
-    host_machine_syncing_folders: |-
-      Syncing folders to the host VM...
-    logging_in: |-
-      Logging in to Docker server...
-    logs_host_state_unknown: |-
-      This container requires a host VM, and the state of that VM
-      is unknown. Run `vagrant up` to verify that the container and
-      its host VM is running, then try again.
-    not_created_skip: |-
-      Container not created. Skipping.
-    not_docker_provider: |-
-      Not backed by Docker provider. Skipping.
-    pull: |-
-      Pulling image '%{image}'...
-    run_command_required: |-
-      `vagrant docker-run` requires a command to execute. This command
-      must be specified after a `--` in the command line. This is used
-      to separate possible machine names and options from the actual
-      command to execute. An example is shown below:
-
-        vagrant docker-run web -- rails new .
-
-    running: |-
-      Container is starting. Output will stream in below...
-    running_detached: |-
-      Container is started detached.
-    ssh_through_host_vm: |-
-      SSH will be proxied through the Docker virtual machine since we're
-      not running Docker natively. This is just a notice, and not an error.
-    synced_folders_changed: |-
-      Vagrant has noticed that the synced folder definitions have changed.
-      With Docker, these synced folder changes won't take effect until you
-      destroy the container and recreate it.
-    waiting_for_running: |-
-      Waiting for container to enter "running" state...
-
-    messages:
-      destroying: |-
-        Deleting the container...
-      not_created: |-
-        The container hasn't been created yet.
-      not_created_original: |-
-        The original container hasn't been created yet. Run `vagrant up`
-        for this machine first.
-      not_running: |-
-        The container is not currently running.
-      preparing: |-
-        Preparing to start the container...
-      provision_no_ssh: |-
-        Provisioners will not be run since container doesn't support SSH.
-      will_not_destroy: |-
-        The container will not be destroyed, since the confirmation was declined.
-      starting: |-
-        Starting container...
-      stopping: |-
-        Stopping container...
-      container_ready: |-
-        Container started and ready for use!
-
-    status:
-      host_state_unknown: |-
-        The host VM for the Docker containers appears to not be running
-        or is currently inaccessible. Because of this, we can't determine
-        the state of the containers on that host. Run `vagrant up` to
-        bring up the host VM again.
-      not_created: |-
-        The environment has not yet been created. Run `vagrant up` to
-        create the environment. If a machine is not created, only the
-        default provider will be shown. So if a provider is not listed,
-        then the machine is not created for that environment.
-      preparing: |-
-        Vagrant is preparing to start this Docker container. Run `vagrant up`
-        to continue.
-      running: |-
-        The container is created and running. You can stop it using
-        `vagrant halt`, see logs with `vagrant docker-logs`, and
-        kill/destroy it with `vagrant destroy`.
-      stopped: |-
-        The container is created but not running. You can run it again
-        with `vagrant up`. If the container always goes to "stopped"
-        right away after being started, it is because the command being
-        run exits and doesn't keep running.
-
-    errors:
-      compose_lock_timeout: |-
-        Vagrant encountered a timeout waiting for the docker compose driver
-        to become available. Please try to run your command again. If you
-        continue to experience this error it may be resolved by disabling
-        parallel execution.
-      docker_compose_not_installed: |-
-        Vagrant has been instructed to use to use the Compose driver for the
-        Docker plugin but was unable to locate the `docker-compose` executable.
-        Ensure that `docker-compose` is installed and available on the PATH.
-      not_created: |-
-        The container hasn't been created yet.
-      not_running: |-
-        The container is not currently running.
-      communicator_non_docker: |-
-        The "docker_hostvm" communicator was specified on a machine that
-        is not provided by the Docker provider. This is a bug with your
-        Vagrantfile. Please contact the creator of your Vagrant environment
-        and notify them to not use this communicator for anything except the
-        "docker" provider.
-      config:
-        both_build_and_image: |-
-          Only one of "build_dir" or "image" can be set
-        build_dir_invalid: |-
-          "build_dir" must exist and contain a Dockerfile
-        build_dir_or_image: |-
-          One of "build_dir" or "image" must be set
-        compose_configuration_hash: |-
-          "compose_configuration" must be a hash
-        compose_force_vm: |-
-          Docker compose is not currently supported from within proxy VM.
-        create_args_array: |-
-          "create_args" must be an array
-        invalid_link: |-
-          Invalid link (should be 'name:alias'): "%{link}"
-        invalid_vagrantfile: |-
-          "vagrant_vagrantfile" must point to a Vagrantfile that exists.
-      docker_provider_nfs_without_privileged: |-
-        You've configured a NFS synced folder but didn't enable privileged
-        mode for the container. Please set the `privileged` option to true
-        on the provider block from your Vagrantfile, recreate the container
-        and try again.
-      docker_provider_image_not_configured: |-
-        The base Docker image has not been set for the '%{name}' VM!
-      execute_error: |-
-        A Docker command executed by Vagrant didn't complete successfully!
-        The command run along with the output from the command is shown
-        below.
-
-        Command: %{command}
-
-        Stderr: %{stderr}
-
-        Stdout: %{stdout}
-      exec_command_required: |-
-        The "docker-exec" command requires a command to execute. This command
-        must be specified after a "--" in the command line. This is used to
-        separate machine name and options from the actual command to execute.
-        An example is show below:
-
-          $ vagrant docker-exec -t nginx -- bash
-
-      host_vm_communicator_not_ready: |-
-        The Docker provider was able to bring up the host VM successfully
-        but the host VM is still reporting that SSH is unavailable. This
-        sometimes happens with certain providers due to bugs in the
-        underlying hypervisor, and can be fixed with a `vagrant reload`.
-        The ID for the host VM is shown below for convenience.
-
-        If this does not fix it, please verify that the host VM provider
-        is functional and properly configured.
-
-        Host VM ID: %{id}
-      package_not_supported: |-
-        The "package" command is not supported with the Docker provider.
-        If you'd like to commit or push your Docker container, please SSH
-        into the host VM (if there is one), and run `docker commit` and
-        so on manually.
-      state_not_running: |-
-        The container never entered the "running" state, or entered it
-        briefly but reverted back to another state. Please verify that
-        the configuration of the container is correct.
-
-        If you meant for this container to not remain running, please
-        set the Docker provider configuration "remains_running" to "false":
-
-          config.vm.provider "docker" do |d|
-            d.remains_running = false
-          end
-
-      state_stopped: |-
-        The container started either never left the "stopped" state or
-        very quickly reverted to the "stopped" state. This is usually
-        because the container didn't execute a command that kept it running,
-        and usually indicates a misconfiguration.
-
-        If you meant for this container to not remain running, please
-        set the Docker provider configuration "remains_running" to "false":
-
-          config.vm.provider "docker" do |d|
-            d.remains_running = false
-          end
-
-      suspend_not_supported: |-
-        The "suspend" command is not supported with the Docker provider.
-        Docker containers don't natively support suspend. If you're using
-        a host machine, you can suspend the host machine by finding it
-        in `vagrant global-status` and using `vagrant suspend <id>`.
-      synced_folder_non_docker: |-
-        The "docker" synced folder type can't be used because the  provider
-        in use is not Docker. This synced folder type only works with the
-        Docker provider. The provider this machine is using is: %{provider}
-      vagrantfile_not_found: |-
-        The configured host VM Vagrantfile could not be found. Please fix
-        the Vagrantfile for this Docker environment to point to a valid
-        host VM.

data/vendor/bundle/ruby/2.5.0/bundler/gems/vagrant-04f7215b5e3f/templates/locales/providers_hyperv.yml

@@ -1,108 +0,0 @@
-en:
-  vagrant_hyperv:
-    choose_switch: |-
-      Please choose a switch to attach to your Hyper-V instance.
-      If none of these are appropriate, please open the Hyper-V manager
-      to create a new virtual switch.
-    message_already_running: |-
-      Hyper-V instance already running.
-    message_not_created: |-
-      VM not created. Moving on...
-    message_not_running: |-
-      Hyper-V machine isn't running. Can't SSH in!
-
-    config:
-      invalid_auto_start_action: |-
-        The requested auto start action for the Hyper-V VM is not a
-        valid action. Please provide a valid action and run the command
-        again.
-
-          Received: %{action}
-          Allowed: %{allowed_actions}
-      invalid_auto_stop_action: |-
-        The requested auto stop action for the Hyper-V VM is not a
-        valid action. Please provide a valid action and run the command
-        again.
-
-          Received: %{action}
-          Allowed: %{allowed_actions}
-      invalid_integration_services_type: |-
-        Invalid type provided for `vm_integration_services`. Type received
-        is `%{received}` but `Hash` was expected.
-      invalid_integration_services_entry: |-
-        The `%{entry_name}` entry in the `vm_integration_services` is set
-        to an unexpected value.
-
-          Received: %{entry_value}
-          Allowed: true, false
-      differencing_disk_deprecation: |-
-        The `differencing_disk` configuration option is deprecated and should
-        no longer be used. The `linked_clone` configuration option should
-        be used instead.
-    errors:
-      admin_required: |-
-        The Hyper-V provider requires that Vagrant be run with
-        administrative privileges. This is a limitation of Hyper-V itself.
-        Hyper-V requires administrative privileges for management
-        commands. Please restart your console with administrative
-        privileges and try again.
-      box_invalid: |-
-        The box you're using with the Hyper-V provider ('%{name}')
-        is invalid. A Hyper-V box should contain both a
-        "Virtual Machines" and a "Virtual Hard Disks" folder that are
-        created as part of exporting a Hyper-V machine.
-
-        Within these directories, Vagrant expects to find the
-        virtual machine configuration as well as the root hard disk.
-
-        The box you're attempting to use is missing one or both of
-        these directories or does not contain the files expected. Verify
-        that you added the correct box. If this problem persists,
-        please contact the creator of the box for assistance.
-      ip_addr_timeout: |-
-        Hyper-V failed to determine your machine's IP address within the
-        configured timeout. Please verify the machine properly booted and
-        the network works. To do this, open the Hyper-V manager, find your
-        virtual machine, and connect to it.
-
-        The most common cause for this error is that the running virtual
-        machine doesn't have the latest Hyper-V integration drivers. Please
-        research for your operating system how to install these in order
-        for the VM to properly communicate its IP address to Hyper-V.
-      no_switches: |-
-        There are no virtual switches created for Hyper-V! Please open
-        the Hyper-V Manager, go to the "Virtual Switch Manager", and create
-        at least one virtual switch.
-
-        A virtual switch is required for Vagrant to create a Hyper-V
-        machine that is connected to a network so it can access it.
-
-        For more help, please see the documentation on the Vagrant website
-        for Hyper-V.
-      powershell_features_disabled: |-
-        The Hyper-V cmdlets for PowerShell are not available! Vagrant
-        requires these to control Hyper-V. Please enable them in the
-        "Windows Features" control panel and try again.
-      powershell_error: |-
-        An error occurred while executing a PowerShell script. This error
-        is shown below. Please read the error message and see if this is
-        a configuration error with your system. If it is not, then please
-        report a bug.
-
-        Script: %{script}
-        Error:
-
-        %{stderr}
-      powershell_required: |-
-        The Vagrant Hyper-V provider requires PowerShell to be available.
-        Please make sure "powershell.exe" is available on your PATH.
-      windows_required: |-
-        The Hyper-V provider only works on Windows. Please try to
-        use another provider.
-      system_access_required: |-
-        Hyper-V access check has failed for the configured destination. This
-        is usually caused by running on a non-system drive which is missing
-        required permissions. Running the following command may resolve the
-        problem:
-
-          icacls.exe %{root_dir} /T /Q /grant "NT AUTHORITY\SYSTEM:(IO)(CI)(F)"

data/vendor/bundle/ruby/2.5.0/bundler/gems/vagrant-04f7215b5e3f/templates/locales/synced_folder_smb.yml

@@ -1,95 +0,0 @@
-en:
-  vagrant_sf_smb:
-    mounting: |-
-      Mounting SMB shared folders...
-    mounting_single: |-
-      %{host} => %{guest}
-    preparing: |-
-      Preparing SMB shared folders...
-    warning_password: |-
-      You will be asked for the username and password to use for the SMB
-      folders shortly. Please use the proper username/password of your
-      account.
-    incorrect_credentials: |-
-      Credentials incorrect. Please try again.
-
-    uac:
-      prune_warning: |-
-        Vagrant requires administrator access for pruning SMB shares and
-        may request access to complete removal of stale shares.
-      create_warning: |-
-        Vagrant requires administrator access to create SMB shares and
-        may request access to complete setup of configured shares.
-    errors:
-      not_supported: |-
-        It appears your machine doesn't support SMB, has not been
-        properly configured for SMB, or there is not an adapter to
-        enable SMB on this machine for Vagrant. Ensure SMB host
-        functionality is available on this machine and try again.
-      start_failed: |-
-        Vagrant failed to automatically start the SMB service. Ensure the
-        required services can be started and try again.
-
-        Command: %{command}
-
-        Stderr: %{stderr}
-
-        Stdout: %{stdout}
-      credentials_missing: |-
-        Vagrant SMB synced folders require the account password to be stored
-        in an NT compatible format. Please update your sharing settings to
-        enable a Windows compatible password and try again.
-      credentials_request_error: |-
-        Vagrant failed to receive credential information required for preparing
-        an SMB share.
-      define_share_failed: |-
-        Exporting an SMB share failed! Details about the failure are shown
-        below. Please inspect the error message and correct any problems.
-
-        Host path: %{host}
-
-        Stderr: %{stderr}
-
-        Stdout: %{stdout}
-      prune_share_failed: |-
-        Pruning an SMB share failed! Details about the failure are shown
-        below. Please inspect the error message and correct any problems.
-
-        Share name: %{name}
-
-        Stderr: %{stderr}
-
-        Stdout: %{stdout}
-      name_error: |-
-        Vagrant is unable to setup a requested SMB share. An SMB share already
-        exists with the given name.
-
-        Share name: %{name}
-
-        Current path: %{existing_path}
-
-        Requested path: %{path}
-      list_failed: |-
-        Vagrant failed to generate a list of local SMB shares. Please try
-        running the command again.
-      no_routable_host_addr: |-
-        We couldn't detect an IP address that was routable to this
-        machine from the guest machine! Please verify networking is properly
-        setup in the guest machine and that it is able to access this
-        host.
-
-        As another option, you can manually specify an IP for the machine
-        to mount from using the `smb_host` option to the synced folder.
-      powershell_version: |-
-        PowerShell version 3 or later is required for SMB synced folders
-        to work on Windows. You have version: '%{version}'. Please update
-        your PowerShell installation.
-      windows_admin_required: |-
-        SMB shared folders require running Vagrant with administrative
-        privileges. This is a limitation of Windows, since creating new
-        network shares requires admin privileges. Please try again in a
-        console with proper permissions or use another synced folder type.
-      windows_host_required: |-
-        SMB shared folders are only available when Vagrant is running
-        on Windows. The guest machine can be running non-Windows. Please use
-        another synced folder type.

data/vendor/bundle/ruby/2.5.0/bundler/gems/vagrant-04f7215b5e3f/templates/nfs/exports.erb

@@ -1,5 +0,0 @@
-# VAGRANT-BEGIN: <%= user %> <%= uuid %>
-<% folders.each do |dirs, opts| %>
-<%= dirs.map { |d| "\"#{d}\"" }.join(" ") %> <%= ips.join(" ") %> <%=opts[:bsd__compiled_nfs_options] %>
-<% end %>
-# VAGRANT-END: <%= user %> <%= uuid %>

data/vendor/bundle/ruby/2.5.0/bundler/gems/vagrant-04f7215b5e3f/templates/nfs/exports_freebsd.erb

@@ -1,5 +0,0 @@
-# VAGRANT-BEGIN: <%= user %> <%= uuid %>
-<% folders.each do |dirs, opts| %>
-<%= dirs.map { |d| "#{d}" }.join(" ") %> <%=opts[:bsd__compiled_nfs_options] %> <%= ips.join(" ") %>
-<% end %>
-# VAGRANT-END: <%= user %> <%= uuid %>

data/vendor/bundle/ruby/2.5.0/bundler/gems/vagrant-04f7215b5e3f/templates/nfs/exports_linux.erb

@@ -1,7 +0,0 @@
-# VAGRANT-BEGIN: <%= user %> <%= uuid %>
-<% ips.each do |ip| %>
-<% folders.each do |name, opts| %>
-"<%= opts[:hostpath] %>" <%= ip %>(<%= opts[:linux__nfs_options].join(",") %>)
-<% end %>
-<% end %>
-# VAGRANT-END: <%= user %> <%= uuid %>

data/vendor/bundle/ruby/2.5.0/bundler/gems/vagrant-04f7215b5e3f/templates/package_Vagrantfile.erb

@@ -1,11 +0,0 @@
-Vagrant::Config.run do |config|
-  # This Vagrantfile is auto-generated by `vagrant package` to contain
-  # the MAC address of the box. Custom configuration should be placed in
-  # the actual `Vagrantfile` in this box.
-  config.vm.base_mac = "<%= base_mac %>"
-end
-
-# Load include vagrant file if it exists after the auto-generated
-# so it can override any of the settings
-include_vagrantfile = File.expand_path("../include/_Vagrantfile", __FILE__)
-load include_vagrantfile if File.exist?(include_vagrantfile)

data/vendor/bundle/ruby/2.5.0/bundler/gems/vagrant-04f7215b5e3f/templates/provisioners/chef_client/client.erb

@@ -1,41 +0,0 @@
-log_level          <%= log_level.inspect %>
-log_location       STDOUT
-verbose_logging    <%= verbose_logging.inspect %>
-<% if node_name %>
-node_name          "<%= node_name %>"
-<% end %>
-ssl_verify_mode    :verify_none
-chef_server_url    "<%= chef_server_url %>"
-
-validation_client_name "<%= validation_client_name %>"
-validation_key         "<%= validation_key %>"
-client_key             "<%= client_key %>"
-
-encrypted_data_bag_secret <%= encrypted_data_bag_secret.inspect %>
-
-<% if environment %>
-environment        "<%= environment %>"
-<% end %>
-
-file_cache_path    "<%= file_cache_path %>"
-file_backup_path   "<%= file_backup_path %>"
-
-http_proxy <%= http_proxy.inspect %>
-http_proxy_user <%= http_proxy_user.inspect %>
-http_proxy_pass <%= http_proxy_pass.inspect %>
-https_proxy <%= https_proxy.inspect %>
-https_proxy_user <%= https_proxy_user.inspect %>
-https_proxy_pass <%= https_proxy_pass.inspect %>
-no_proxy <%= no_proxy.inspect %>
-
-pid_file           "/var/run/chef/chef-client.pid"
-
-Mixlib::Log::Formatter.show_time = true
-
-<% if formatter %>
-add_formatter "<%= formatter %>"
-<% end %>
-
-<% if custom_configuration -%>
-Chef::Config.from_file "<%= custom_configuration %>"
-<% end -%>

data/vendor/bundle/ruby/2.5.0/bundler/gems/vagrant-04f7215b5e3f/templates/provisioners/chef_solo/solo.erb

@@ -1,52 +0,0 @@
-<% if node_name %>
-node_name "<%= node_name %>"
-<% end %>
-file_cache_path    "<%= file_cache_path %>"
-file_backup_path   "<%= file_backup_path %>"
-cookbook_path <%= cookbooks_path.inspect %>
-<% if roles_path && !roles_path.empty? -%>
-role_path <%= roles_path.size == 1 ? roles_path.first.inspect : roles_path.inspect %>
-<% end -%>
-log_level <%= log_level.inspect %>
-verbose_logging <%= verbose_logging.inspect %>
-
-encrypted_data_bag_secret <%= encrypted_data_bag_secret.inspect %>
-
-<% if data_bags_path && !data_bags_path.empty? -%>
-data_bag_path <%= data_bags_path.size == 1 ? data_bags_path.first.inspect : data_bags_path.inspect %>
-<% end %>
-
-<% if recipe_url -%>
-recipe_url "<%= recipe_url %>"
-<% end -%>
-
-<% if environments_path && !environments_path.empty? -%>
-environment_path <%= environments_path.inspect %>
-<% end -%>
-
-<% if environment -%>
-environment "<%= environment %>"
-<% end -%>
-
-<% if local_mode -%>
-local_mode true
-<% end -%>
-<% if nodes_path && !nodes_path.empty? -%>
-node_path <%= nodes_path.inspect %>
-<% end -%>
-
-http_proxy <%= http_proxy.inspect %>
-http_proxy_user <%= http_proxy_user.inspect %>
-http_proxy_pass <%= http_proxy_pass.inspect %>
-https_proxy <%= https_proxy.inspect %>
-https_proxy_user <%= https_proxy_user.inspect %>
-https_proxy_pass <%= https_proxy_pass.inspect %>
-no_proxy <%= no_proxy.inspect %>
-
-<% if formatter -%>
-add_formatter "<%= formatter %>"
-<% end %>
-
-<% if custom_configuration -%>
-Chef::Config.from_file "<%= custom_configuration %>"
-<% end -%>

data/vendor/bundle/ruby/2.5.0/bundler/gems/vagrant-04f7215b5e3f/templates/provisioners/chef_zero/zero.erb

@@ -1,45 +0,0 @@
-<% if node_name %>
-node_name "<%= node_name %>"
-<% end %>
-file_cache_path    "<%= file_cache_path %>"
-file_backup_path   "<%= file_backup_path %>"
-cookbook_path <%= cookbooks_path.inspect %>
-<% if roles_path %>
-role_path <%= roles_path.size == 1 ? roles_path.first.inspect : roles_path.inspect %>
-<% end %>
-log_level <%= log_level.inspect %>
-verbose_logging <%= verbose_logging.inspect %>
-
-<% if !enable_reporting %>
-enable_reporting <%= enable_reporting.inspect %>
-<% end %>
-
-encrypted_data_bag_secret <%= encrypted_data_bag_secret.inspect %>
-
-<% if data_bags_path -%>
-data_bag_path <%= data_bags_path.size == 1 ? data_bags_path.first.inspect : data_bags_path.inspect %>
-<% end %>
-
-<% if environments_path %>
-environment_path <%= environments_path.inspect %>
-<% end -%>
-
-<% if environment %>
-environment "<%= environment %>"
-<% end -%>
-
-<% if local_mode -%>
-chef_zero.enabled true
-local_mode true
-<% end -%>
-<% if nodes_path -%>
-node_path <%= nodes_path.inspect %>
-<% end -%>
-
-<% if formatter %>
-add_formatter "<%= formatter %>"
-<% end %>
-
-<% if custom_configuration -%>
-Chef::Config.from_file "<%= custom_configuration %>"
-<% end -%>

data/vendor/bundle/ruby/2.5.0/bundler/gems/vagrant-04f7215b5e3f/templates/rgloader.rb

@@ -1,9 +0,0 @@
-# This file loads the proper rgloader/loader.rb file that comes packaged
-# with Vagrant so that encoded files can properly run with Vagrant.
-
-if ENV["VAGRANT_INSTALLER_EMBEDDED_DIR"]
-  require File.expand_path(
-    "rgloader/loader", ENV["VAGRANT_INSTALLER_EMBEDDED_DIR"])
-else
-  raise "Encoded files can't be read outside of the Vagrant installer."
-end

data/vendor/bundle/ruby/2.5.0/bundler/gems/vagrant-04f7215b5e3f/test/acceptance/base.rb

@@ -1,2 +0,0 @@
-require "vagrant-spec/acceptance"
-require_relative "shared/context_virtualbox"