|
25 | 25 | size = "s-1vcpu-1gb"; |
26 | 26 | }; |
27 | 27 | resource.digitalocean_record.${name} = { |
| 28 | + name = name; |
28 | 29 | domain = "example.com"; |
29 | 30 | type = "A"; |
30 | | - name = name; |
31 | 31 | value = "\${digitalocean_droplet.${name}.ipv4_address}"; |
32 | 32 | }; |
33 | 33 | }; |
@@ -68,10 +68,12 @@ resource "digitalocean_record" "site" { |
68 | 68 | {{% /codetabs %}} |
69 | 69 |
|
70 | 70 | {{< features >}} |
71 | | -{{< feature title="Full Nix language" >}}Use let-bindings, imports, conditionals, and module composition with the same language you already use for NixOS. For a comparison, see [terranix vs. HCL](/docs/getting-started/vs-hcl/).{{< /feature >}} |
72 | | -{{< feature title="NixOS module system" >}}Type-checked configuration with sensible defaults, overrides, and reusable modules. For a comparison, see [Modules](/docs/modules/).{{< /feature >}} |
73 | | -{{< feature title="nixpkgs ecosystem" >}}Tap into `fetchgit`, `fetchurl`, `writers`, and pin Terraform / OpenTofu versions and providers reproducibly.{{< /feature >}} |
74 | | -{{< feature title="Documentation generator" >}}Generate JSON or man-page documentation straight from your `config.nix` module options.{{< /feature >}} |
| 71 | +{{< feature title="Full Nix language" >}}Use let-bindings, imports, conditionals, and module composition. Allow for nested structures and re-use. For a comparison, see [terranix vs. HCL](/docs/getting-started/vs-hcl/).{{< /feature >}} |
| 72 | +{{< feature title="NixOS module system" >}}Type-checked configuration with sensible defaults, overrides, and reusable modules. Opt-in flake support. For a comparison, see [Modules](/docs/modules/).{{< /feature >}} |
| 73 | +{{< feature title="nixpkgs ecosystem" >}}Tap into `fetchgit`, `fetchurl`, `writers`, work and pin Terraform / OpenTofu versions and providers reproducibly.{{< /feature >}} |
| 74 | +{{< feature title="Transcend IAC boundaries" >}}Combine your terranix configuration with arbitrary Nix: If you can express it with Nix, you can provision it. Conversely, if you've provisioned it, you can reference it elsewhere. See example.{{< /feature >}} |
| 75 | +{{< feature title="Reproducible builds" >}}Pin Terraform / OpenTofu and every provider as Nix derivations, so the same `config.nix` produces an identical plan. Work across repos.{{< /feature >}} |
| 76 | +{{< feature title="Multi-environment" >}}Generate different Terraform JSON outputs from the same module by passing env, region, or workspace arguments as plain Nix function inputs.{{< /feature >}} |
75 | 77 | {{< /features >}} |
76 | 78 |
|
77 | 79 | {{< latest-news >}} |
0 commit comments