ignition_config
Renders an ignition configuration as JSON. It contains all the disks, partitions, arrays, filesystems, files, users, groups and units.
Example Usage
data "ignition_config" "example" { systemd = [ "${data.ignition_systemd_unit.example.id}", ] }
Argument Reference
The following arguments are supported:
-
disks
- (Optional) The list of disks to be configured and their options. -
arrays
- (Optional) The list of RAID arrays to be configured. -
filesystems
- (Optional) The list of filesystems to be configured and/or used in theignition_file
,ignition_directory
, andignition_link
resources. -
files
- (Optional) The list of files to be written. -
directories
- (Optional) The list of directories to be created. -
links
- (Optional) The list of links to be created. -
systemd
- (Optional) The list of systemd units. Describes the desired state of the systemd units. -
networkd
- (Optional) The list of networkd units. Describes the desired state of the networkd files. -
users
- (Optional) The list of accounts to be added. -
groups
- (Optional) The list of groups to be added. -
append
- (Optional) Any number of blocks with the configs to be appended to the current config. -
replace
- (Optional) A block with config that will replace the current.
The append
and replace
blocks supports:
-
source
- (Required) The URL of the config. Supported schemes are http, https, tftp, s3, and data. When using http, it is advisable to use the verification option to ensure the contents haven't been modified. -
verification
- (Optional) The hash of the config, in the form <type>-<value> where type is sha512.
Attributes Reference
The following attributes are exported:
-
rendered
- The final rendered template.
© 2018 HashiCorpLicensed under the MPL 2.0 License.
https://www.terraform.io/docs/providers/ignition/d/config.html