docs: slide 14 — add a small HCL example illustrating block anatomy
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -653,10 +653,18 @@
|
|||||||
<section class="s-tf">
|
<section class="s-tf">
|
||||||
<h2>HCL: HashiCorp Configuration Language</h2>
|
<h2>HCL: HashiCorp Configuration Language</h2>
|
||||||
<p>Declarative, human-readable — pure JSON works too.</p>
|
<p>Declarative, human-readable — pure JSON works too.</p>
|
||||||
|
<pre><code class="language-hcl" data-trim>
|
||||||
|
resource "openstack_compute_instance_v2" "web" {
|
||||||
|
name = "finistdevs-web"
|
||||||
|
flavor_name = "b3-8"
|
||||||
|
tags = ["web", "demo"]
|
||||||
|
}
|
||||||
|
</code></pre>
|
||||||
<aside class="notes">
|
<aside class="notes">
|
||||||
<ul>
|
<ul>
|
||||||
<li>Declarative: you describe the desired end state, not the steps.</li>
|
<li>Declarative: you describe the desired end state, not the steps.</li>
|
||||||
<li>HCL is the common language across all HashiCorp tools.</li>
|
<li>HCL is the common language across all HashiCorp tools.</li>
|
||||||
|
<li>Block anatomy: a block type (<code>resource</code>), two labels (provider type + local name), then <code>key = value</code> arguments — strings, lists, etc.</li>
|
||||||
</ul>
|
</ul>
|
||||||
</aside>
|
</aside>
|
||||||
</section>
|
</section>
|
||||||
|
|||||||
Reference in New Issue
Block a user