* provider/ignition: migration from resources to data resources
* website: provider/ignition documention updated to data resources
* provider/ignition: backwards compatibility support for old resources
@ -13,7 +13,7 @@ Renders an ignition configuration as JSON. It contains all the disks, partition
## Example Usage
```
resource "ignition_config" "example" {
data "ignition_config" "example" {
systemd = [
"${ignition_systemd_unit.example.id}",
]
@ -46,7 +46,7 @@ The following arguments are supported:
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.
@ -19,16 +19,16 @@ Use the navigation to the left to read about the available resources.
This config will write a single service unit (shown below) with the contents of an example service. This unit will be enabled as a dependency of multi-user.target and therefore start on boot
```
# Systemd unit resource containing the unit definition
resource "ignition_systemd_unit" "example" {
name = "example.service"
# Systemd unit data resource containing the unit definition