daily-email: add 2023-03-08
This commit is contained in:
parent
ccdea9d5c6
commit
19d9d3089e
19
website/src/daily-emails/2023-03-08.md
Normal file
19
website/src/daily-emails/2023-03-08.md
Normal file
|
@ -0,0 +1,19 @@
|
|||
---
|
||||
title: >
|
||||
Automating infrastructure with IaC
|
||||
pubDate: 2023-03-08
|
||||
permalink: >
|
||||
archive/2023/03/08/automating-infrastructure-with-iac
|
||||
tags:
|
||||
- devops
|
||||
---
|
||||
|
||||
Are you responsible for creating and maintaining resources like GitHub repositories, DigitalOcean servers, Amazon S3 buckets and Cloudfront distributions or DNS records in Cloudflare?
|
||||
|
||||
Do you do that through the various web UIs?
|
||||
|
||||
I'd recommend looking into infrastructure as code tools such as Ansible, Terraform and Pulumi.
|
||||
|
||||
You can create, manage and destroy these resources by writing text files rather than clicking around in web UIs, which you can store and share using version control tools.
|
||||
|
||||
Infrastructure as code (IaC) tools are something that I use when working with infrastructure, whether it's for a client project or [a talk demo](https://github.com/opdavies/rebuilding-acquia/blob/4efe94398f4d8715d22ca677756beb36017d4e74/main.tf) (this uses Terraform to create an Amazon S3 bucket and Cloudflare distribution, link it to an SSL certificate and create my DNS records - all automatically).
|
Loading…
Reference in a new issue