Christopher McGrath

Terraform's Import block functionality will help give a lot of companies the ability to bring their existing infrastructure under a unified code base. Now with the ability to use for_each inside their import block this video shows a cool way to utilize that feature to build on top of your existing pipelines without having to re-engineer anything.

4

🚀 Crazy thing to think about — when do the following Terraform files get created? 🤔 📁 .terraform/ 🔒 .terraform.lock.hcl 📜 .terraform.lock.info 🗂️ terraform.tfstate 🗃️ terraform.tfstate.backup Here’s the breakdown: 📁 .terraform/ Created when you initialize your Terraform project with the command terraform init. It contains important metadata, providers, and module information necessary for Terraform to work. 🔒 .terraform.lock.hcl This file is generated after terraform init and locks provider versions, ensuring consistency across different environments. 🔑 📜 .terraform.lock.info Temporary file created during the execution of terraform apply. It holds the state of the providers being used and is automatically removed once the apply command completes successfully. 🗂️ terraform.tfstate This state file is created or updated after running terraform apply, storing the current state of your infrastructure. It helps Terraform track the resources it manages. 🌍 🗃️ terraform.tfstate.backup This backup file is generated whenever you modify or destroy resources. It acts as a fallback in case something goes wrong during a state change. 🚧 Refer to my below article what happen we you execute terraform init #Terraform #InfrastructureAsCode #DevOps #Iac #AWS

25

Hey Fam! Guess what? I just levelled up my Terraform game, and I gotta share the deets with you all! Check out few drops on Terraform Workflow below. #TERRAFORMWORKFLOW: 1. #Write: Define your infrastructure using HashiCorp Configuration Language (HCL) in .tf files. Your infrastructure will be designed according to this code. 2. #Initialize: We use a command “terraform init” for initialize working directory. This command downloads the necessary provider plugins and sets up your configuration for further actions. 3. #Plan (terraform plan): We use “terraform plan” command to review and generate an execution plan.  Terraform compares the current state of your infrastructure with your configuration files and shows what changes will be made. 4. #Apply (terraform apply): We use a command “terraform apply” to execute the planned changes. Terraform will create, modify, or delete resources to match your configuration. We need to review the proposed changes and confirm applying them. 5. #Destroy: We use “terraform destroy” command when we need to destroy the infrastructure.  This command will remove all resources defined in your configuration. By following this workflow, we can ensure that our infrastructure is consistent, repeatable, and manageable. Terraform not only automates provisioning but also provides visibility and control over your infrastructure changes. #DevOps #Terraform #InfrastructureAsCode #Automation #HashiCorp #Workflow Keep rockin' those infrastructure-as-code vibes!

5

AWS Lambda is an almost instinctual choice when it comes to building on AWS Cloud (and why not? It's awesome!). But are Lambda functions - and the custom libraries and code that comes with them - always the right choice? Particularly for gluing components together? I spend some time exploring the potential of working with native AWS services to produce an event-driven solution with no Lambda or custom code in sight. #aws #eventbridge #software #architecture #serverless

38

6 Comments

Happy Saturday, good people! ☀ I hope all is well. I went out for my usual Saturday morning run and came back to tackle this project. This one in particular was fun because I'm addressing an issue that I personally dealt with. It gave me a chance to work with more on-prem services. Because I'm well versed in dealing with everything in the cloud, especially virtual machines such as EC2 instances, I have an appreciation for the growth and learning that took place debugging this 502 Gateway error. It took me a couple of days to come to a solution, but it was a great learning experience all the way through. Knowing how to ensure 24/7 application availability using Task Scheduler is significant because it directly impacts the reliability and uptime of critical applications. By automating the startup process, we can prevent downtime caused by terminal closures and ensure continuous operation. S.N: It's a major confidence boost when you come into a new role and resolve tickets, no matter how minute they may seem. Each resolution, whether pertaining to an outstanding issue or a quick fix, serves as further confirmation that you belong and you are great at what you do! Here's to more progress and challenging that comfort zone! #techtalk #cloud #devops #devopsengineer #onprem #cloudengineer #devopsengineer #medium

6

Is it time to retire Terraform as you Iac? With rise of the cloud providers tools and services. Terraform without some easier tools and better syntax might be replaced by newer technology the cloud providers are offering. Take a read through this article as they make a good case for this type of transition. https://lnkd.in/eDy4VGxZ

3

3 Comments

I'm a bad SQL Engineer but thank you Anthropic Claude 3.5 sonnet. I'm trying to setup a disk usage autoscaling for my AWS RDS PostgresSQL for the application. I'm at already a benchmark to use based on my current utilization to set the minimum table space disk usage on the database disk. I think I'm gonna try the AWS NVme disk for my Postgres Server disk and see the improvements. NVME disk has a really fast I/O for your database workloads If you have high throughput database read and write operations. But beware of the cost. #softwareengineering #cloudcomputing #postgres #golang #coding #programming #kubernetes

14

2 Comments

Enterprise SRE or tech leader? Years of observability investments, yet teams remain siloed, problems still getting passed around while end-user experience still suffers? Struggling to bridge the gap between observability tools and real-world business impact? You're not alone. Evolutio understands these frustrations. Their expertise lies in bridging the gaps between tools, teams, and processes to finally unlock the true value of observability solutions. Their Chicago event (with remote options) is about actionable strategies for driving change and seeing real results. 👉 [Event Title: Why OpenTelemetry Matters for Observability & User Experience] 👉 https://lnkd.in/gVWu5UZK #observability #SRE #techleadership #ChicagoTech #OpenTelemetry This post and opinions here are my own and are not endorsed or sponsored by Evolutio or Cisco. I just want to make that clear folks. I only post things I endorse and rarely re-post (and probably miss some things I should!)

12

Here are my thoughts on #observability, in no particular order: If your application doesn't produce any #logs (#metrics, #spans, you name it), troubleshooting becomes impossible. You may not even know if it's running. This is especially problematic when your application logs only during usage, but it's not being used. On the flip side, if your application generates too many logs, it can also be challenging to troubleshoot, even if you have log querying tools. Logging "Health check succeeded!" every second for routine health checks contributes to log overload, compounding the previous issue. When log entries are excessively long (structured or not, someone will have to look at your logs at some point). When structured logs contain large, embedded JSON objects. When structured logs embed lengthy lists with line breaks (which are encoded). When stack traces dive into the internals of your HTTP server (or any other third-party library). When the same information is logged repeatedly across 15 layers of error handling. When you cannot attribute an error to an invocation or input parameters. When you log sensitive information. Happy logging!

8

Do you work with Kyverno in Kubernetes? Help build a new IT professional certification: #Kyverno Certified Associate (KCA) by telling us what it takes to be successful in your role. Take the survey today: https://lnkd.in/gH9zbypR  #Kubernetes #DevOps #CloudNative

30

Chapter 7 of Terraform in Depth has been released to the early access program! This is the chapter on Continuous Integration and Code Quality. It's absolutely my favorite chapter and the one that teams already using Terraform will get the most out of. This is the largest chapter in the book so far (in fact we had to split CD off from the typically CICD bundle because the content for both was so huge). In it I break down all of the different tools in the Terraform ecosystem for maintaining code quality, with examples of how to use them. I also talk about how you can validate your code against both Terraform and OpenTofu. This chapter also spawned an entire open source project, which I'll be discussing more in a future post! #OpenTofu #Terraform https://mng.bz/vPem

57

1 Comment

Both virtualization and containerization are powerful methods for optimizing infrastructure and deploying applications - each with its own pros and cons. Evaluate your options in this blog and learn how to best drive innovation in your organization.

1

Could Pulumi be the future of IaC? 🤷‍♂️ With its promise of writing infrastructure code in your favorite programming language, Pulumi definitely isn't going unnoticed. 👀 Will it surpass Terraform as the go-to choice? 🤔 I'm keeping a keen eye on this space! #DevOps #InfrastructureAsCode #PulumiVsTerraform

14

You can create your own Kubernetes extension (an Operator) to interact with whatever API you'd like (as long as you have access or it's public). When you create an Operator, you'd use something like Kubebuilder. Once you figure out a framework (like Kubebuilder) to use, you can use Go to programmatically configure how you want the Operator to look. Here's an example. #kubernetes #devops #platformengineering

73

4 Comments

Shift security left! Read how platform engineering incorporates many of the strong points of #DevOps, automatically baking security into every step of the development process to avoid rework and delays. https://dy.si/uZtkB

2

Containerization is a powerful tool for managing workloads. However, not all workloads are suitable for containerization. In this tech talk I cover out how to handle virtualized workloads that don’t make sense to containerize while leveraging the robust self-healing capabilities of Kubernetes.

9

2 Comments