vaguerent/website/pages/docs/cloud-init/configuration.mdx

44 lines
1.6 KiB
Plaintext

---
layout: docs
page_title: Vagrant Cloud-Init Configuration
sidebar_title: Configuration
description: Documentation of various configuration options for Vagrant cloud-init
---
# Configuration
Vagrant cloud-init has several options that allow users to define a config to be
used with cloud-init.
For more detailed information about these config values and how to use cloud-init,
please read the [official documentation for cloud-init](https://cloudinit.readthedocs.io/en/latest/index.html).
## cloud_init Options
It should be noted that Vagrant will not validate the correctness of the `cloud-init`
config provided, only that a cloud-init config has been provided through `path`
or directly `inline` in a Vagrantfile.
- `content_type` (string) - Required argument that defines the Content-Type of the
given cloud_init config. Vagrant only supports the following options for `content_type`:
+ `"text/cloud-boothook"`
+ `"text/cloud-config"`
+ `"text/cloud-config-archive"`
+ `"text/jinja2"`
+ `"text/part-handler"`
+ `"text/upstart-job"`
+ `"text/x-include-once-url"`
+ `"text/x-include-url"`
+ `"text/x-shellscript"`
- `path` (string) - Path to a file on the host machine that contains
cloud-init user data. This will be added to the multipart user-data file along
with its `content_type`. Incompatible with the `inline` option.
- `inline` (string) - Inline cloud-init user data. This will be added to the
multipart user-data file along with its `content_type`. Incompatible with `path`
option.
Examples of how to define these options can be found in the
[usage documentation](/docs/cloud-init/configuration).