github.com/vtorhonen/terraform@v0.9.0-beta2.0.20170307220345-5d894e4ffda7/website/source/docs/providers/ignition/d/config.html.md (about)

     1  ---
     2  layout: "ignition"
     3  page_title: "Ignition: ignition_config"
     4  sidebar_current: "docs-ignition-datasource-config"
     5  description: |-
     6    Renders an ignition configuration as JSON
     7  ---
     8  
     9  # ignition\_config
    10  
    11  Renders an ignition configuration as JSON. It  contains all the disks, partitions, arrays, filesystems, files, users, groups and units.
    12  
    13  ## Example Usage
    14  
    15  ```
    16  data "ignition_config" "example" {
    17  	systemd = [
    18  		"${ignition_systemd_unit.example.id}",
    19  	]
    20  }
    21  ```
    22  
    23  ## Argument Reference
    24  
    25  The following arguments are supported:
    26  
    27  * `disks` - (Optional) The list of disks to be configured and their options.
    28  
    29  * `arrays` - (Optional) The list of RAID arrays to be configured.
    30  
    31  * `filesystems` - (Optional) The list of filesystems to be configured and/or used in the _ignition_file_ resource.
    32  
    33  * `files` - (Optional) The list of files, rooted in this particular filesystem, to be written.
    34  
    35  * `systemd` - (Optional) The list of systemd units. Describes the desired state of the systemd units.
    36  
    37  * `networkd` - (Optional) The list of networkd units. Describes the desired state of the networkd files.
    38  
    39  * `users` - (Optional) The list of accounts to be added.
    40  
    41  * `groups` - (Optional) The list of groups to be added.
    42  
    43  * `append` - (Optional) A block with config that will replace the current.
    44  
    45  * `replace` - (Optional) Any number of blocks with the configs to be appended to the current config.
    46  
    47  
    48  The `append` and `replace` blocks supports:
    49  
    50  * `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.
    51  
    52  * `verification` - (Optional) The hash of the config, in the form _\<type\>-\<value\>_ where type is sha512.
    53  
    54  ## Attributes Reference
    55  
    56  The following attributes are exported:
    57  
    58  * `rendered` - The final rendered template.