Infrastructure as Code

ब्रीफ़िंग

business/inherited-cloud-estate made the case for defining infrastructure in files and then said, out loud, that it was not going to teach you the tool. This is the tool. You will make the same resource three ways — clicked, scripted, declared — with a stopwatch, so the difference is measured instead of asserted. You will read a plan before you apply it, because the plan is the only safety device in the whole subject. Then a module entirely about the thing that actually hurts: state. What the state file holds, why it holds your secrets in clear text, what a lock is and what happens when two people apply at once, and the recovery when the file and the world disagree — drift you overwrite, drift you keep, a resource somebody deleted by hand, and a state file you lost. Every one of those is reproduced on your own machine, not described. The last module writes a service once and stands it up as two environments from the same code, then destroys the whole thing and rebuilds it against a stopwatch — the artefact the segment exists to produce: a rebuild time you can quote, and the sentence about what quoting it lets your organisation stop being afraid to delete. Nothing here spends money. Where a real cloud resource would bill, a local container, file or generated value stands in for it, and every pack says so plainly. Everything was run against Terraform 1.15.8 before it was written down.

1. 01 The Same Resource, Three Ways

   3 पाठ·2h 21m

   Everybody has clicked a console, written a stand-up script, and been burned by running it twice. Naming those as three points on one line — imperative to declarative — is what makes the rest of the…

2. 02 State, and When It Lies

   3 पाठ·2h 28m

   This is the module the segment is built around. Nearly every hard problem in Terraform is downstream of one decision — where the state lives — and the module arrives at that decision four times from…

3. 03 Write It Once, Then Destroy It

   3 पाठ·2h 27m

   The module-and-environments structure is the setup; the timed destroy-and-rebuild is the payoff. The number itself is not the point — its repeatability is, because a rebuild time you can quote is…

4. 04 The Plan Runs Without You

   3 पाठ·2h 21m

   The first three modules made a change safe to make by hand. This one takes the human out of the loop without taking the safety out, and the through-line is the plan: module 1 read it on a screen,…

अक्सर पूछे जाने वाले

मैं Infrastructure as Code में क्या सीखूँगा?

The tool the cloud course refused to teach. Build the same resource three ways and time the difference, then live in the file that actually breaks: the state file, its secrets in clear, its lock, and the recovery when it and the world disagree. Everything is run against a pinned Terraform and a loca

क्या मुझे पूर्व अनुभव चाहिए?

Infrastructure as Code शुरू करने से पहले कुछ पूर्व ज्ञान की सिफ़ारिश की जाती है।

Infrastructure as Code में कितना समय लगता है?

Infrastructure as Code में 4 मॉड्यूल और 12 पाठ शामिल हैं। आप अपनी गति से सीखते हैं।

मुझे एक्सेस कैसे मिलता है?

Infrastructure as Code किसी भी सशुल्क सब्सक्रिप्शन के साथ शामिल है।