67 lines
2.5 KiB
Markdown
67 lines
2.5 KiB
Markdown
|
---
|
||
|
|
# Name of the whitepaper.
|
||
|
|
title: "Guide: Getting Started with Infrastructure as Code"
|
||
|
|
meta_desc: "Infrastructure as code (IaC) means that you use code to define and manage infrastructure. In this guide, learn how the fundamentals of IaC."
|
||
|
|
|
||
|
|
# Set the whitepaper flag.
|
||
|
|
whitepaper: true
|
||
|
|
|
||
|
|
# A featured resource will display first in the list.
|
||
|
|
featured: false
|
||
|
|
|
||
|
|
# Resources with unlisted as true will not be shown on the webinar list
|
||
|
|
unlisted: false
|
||
|
|
|
||
|
|
# Gated resources will have a registration form and the user will need
|
||
|
|
# to fill out the form before viewing.
|
||
|
|
gated: true
|
||
|
|
|
||
|
|
# The layout of the landing page.
|
||
|
|
type: webinars
|
||
|
|
|
||
|
|
# External resources will link to an external page instead of a resource
|
||
|
|
# landing/registration page. If the resource is external you will need
|
||
|
|
# set the 'block_external_search_index' flag to true so Google does not index
|
||
|
|
# the resource page created.
|
||
|
|
external: false
|
||
|
|
block_external_search_index: false
|
||
|
|
|
||
|
|
# The url slug for the webinar landing page. If this is an external
|
||
|
|
# webinar, use the external URL as the value here.
|
||
|
|
url_slug: "getting-started-with-infrastructure-as-code-guide"
|
||
|
|
|
||
|
|
# The content of the hero section.
|
||
|
|
hero:
|
||
|
|
# The title text in the hero. This also serves as the pages H1.
|
||
|
|
title: "Guide: Getting Started with Infrastructure as Code"
|
||
|
|
|
||
|
|
# Content for the left hand side section of the page.
|
||
|
|
main:
|
||
|
|
# Webinar title.
|
||
|
|
title: "Guide: Getting Started with Infrastructure as Code"
|
||
|
|
# Sortable date. The datetime Hugo will use to sort the webinars in date order.
|
||
|
|
sortable_date: 2021-09-09T10:00:00-07:00
|
||
|
|
# Duration of the whitepaper.
|
||
|
|
duration: "7 pages"
|
||
|
|
# Description of the whitepaper.
|
||
|
|
description: |
|
||
|
|
Infrastructure as code (IaC) means that you use code to define and manage infrastructure rather than using manual processes. More broadly, and perhaps more importantly, IaC is about bringing software engineering principles and approaches to cloud infrastructure. In this guide, explore the fundamentals of IaC and how to get started setting up your environment.
|
||
|
|
|
||
|
|
# The whitepaper authors
|
||
|
|
presenters:
|
||
|
|
- name: George Huang
|
||
|
|
role: Director of Product Marketing, Pulumi
|
||
|
|
|
||
|
|
# A bullet point list containing what the user will learn.
|
||
|
|
learn:
|
||
|
|
- Why does Infrastructure as Code (IaC) matter?
|
||
|
|
- Important considerations when using IaC.
|
||
|
|
- How to get started with IaC.
|
||
|
|
- IaC best practices.
|
||
|
|
|
||
|
|
# The right hand side form section.
|
||
|
|
form:
|
||
|
|
# HubSpot form id.
|
||
|
|
hubspot_form_id: "c726d203-f1ce-4b16-a6c9-b66a3d9132ce"
|
||
|
|
---
|