⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️

[!IMPORTANT]
Documentation Update: Product documentation previously located in /website has moved to the hashicorp/web-unified-docs repository, where all product documentation is now centralized. Please make contributions directly to web-unified-docs, since changes to /website in this repository will not appear on developer.hashicorp.com. ⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️

Experimental Feature Flag

Some features that aren't ready for release can be enabled through this feature flag. There are a couple of different ways of going about enabling these features. It is also worth noting that Vagrant will not validate the existence of a feature flag.

For example if you are on Linux or Mac, and you wish to enable every single experimental feature, you can set the flag to "on" by setting it to 1:

export VAGRANT_EXPERIMENTAL="1"

You can also enable some or many features if there are specific ones you would like, but don't want every single feature enabled:

# Only enables feature_one
export VAGRANT_EXPERIMENTAL="feature_one"

# Enables both feature_one and feature_two
export VAGRANT_EXPERIMENTAL="feature_one,feature_two"

Valid experimental features

~> Advanced topic! This is an advanced topic for use only if you want to use new Vagrant features. If you are just getting started with Vagrant, you may safely skip this section.

This is a list of all the valid experimental features that Vagrant recognizes:

• none_communicator - Allows Vagrant to manage remote machines without the ability to connect to them for configuration/provisioning.