b58709aa91
* provider/ignition: migration from resources to data resources * website: provider/ignition documention updated to data resources * provider/ignition: backwards compatibility support for old resources
1.8 KiB
layout, page_title, sidebar_current, description
| layout | page_title | sidebar_current | description |
|---|---|---|---|
| ignition | Ignition: ignition_config | docs-ignition-datasource-config | Renders an ignition configuration as JSON |
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 = [
"${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 the ignition_file resource. -
files- (Optional) The list of files, rooted in this particular filesystem, to be written. -
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) A block with config that will replace the current. -
replace- (Optional) Any number of blocks with the configs to be appended to the current config.
The append and replace blocks supports:
-
source- (Required) The URL of the config. Supported schemes are http. Note: 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.