vagrant/website/source/docs/experimental/index.html.md

57 lines
1.9 KiB
Markdown
Raw Normal View History

2019-01-22 23:43:19 +00:00
---
layout: "docs"
page_title: "Vagrant Experimental Feature Flag"
sidebar_current: "experimental"
description: |-
Introduction to Vagrants Experimental Feature Flag
---
# Experimental Feature Flag
Some features that aren't ready for release can be enabled through this feature
2019-02-07 22:11:08 +00:00
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
2019-02-07 22:11:08 +00:00
flag.
2019-01-22 23:43:19 +00:00
2019-02-07 22:11:08 +00:00
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`:
2019-01-22 23:43:19 +00:00
```shell
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:
```shell
# Only enables feature_one
export VAGRANT_EXPERIMENTAL="feature_one"
```
```shell
# Enables both feature_one and feature_two
export VAGRANT_EXPERIMENTAL="feature_one,feature_two"
```
2019-02-07 22:11:08 +00:00
## Valid experimental features
2019-01-22 23:43:19 +00:00
<div class="alert alert-warning">
<strong>Advanced topic!</strong> This is an advanced topic for use only if
2019-02-07 22:11:08 +00:00
you want to use new Vagrant features. If you are just getting
2019-01-22 23:43:19 +00:00
started with Vagrant, you may safely skip this section.
</div>
This is a list of all the valid experimental features that Vagrant recognizes:
### `typed_triggers`
Enabling this feature allows triggers to recognize and execute `:type` triggers.
More information about how these should be used can be found on the [trigger documentation page](/docs/triggers/configuration.html#trigger-types)
2019-08-28 22:09:48 +00:00
### `dependency_provisioners`
Enabling this feature allows all provisioners to specify `before` and `after`
options. These options allow provisioners to be configured to run before or after
any given "root" provisioner. more information about these options can be found
on the [base provisioner documentation page](/docs/provisioning/basic_usage.html)