<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>codewizardly.com | DevOps.</title>
    <description>Tips and tutorials from a DevOps world.</description>
    <link>https://codewizardly.com/</link>
    <atom:link href="https://codewizardly.com/feed.xml" rel="self" type="application/rss+xml"/>
    <pubDate>Sun, 22 Feb 2026 23:19:04 +0000</pubDate>
    <lastBuildDate>Sun, 22 Feb 2026 23:19:04 +0000</lastBuildDate>
    <generator>Jekyll v3.10.0</generator>
    
      <item>
        <title>Testing AWS Lambdas Locally with Docker</title>
        <description>&lt;p&gt;AWS Lambda is a powerful serverless compute service that allows you to run code without provisioning or managing servers. However, testing Lambda functions in a cloud environment can be cumbersome and time-consuming. Fortunately, Docker provides a seamless way to simulate AWS Lambda locally, making the development and testing process much more efficient.&lt;/p&gt; &lt;p&gt;In this post, I’ll guide you through setting up a Docker container to test your AWS Lambda functions written in Golang.&lt;/p&gt; &lt;h2 id=&quot;prerequisites&quot;&gt;Prerequisites&lt;/h2&gt; &lt;p&gt;Before we dive in, make sure you have the following installed on your machine:&lt;/p&gt; &lt;ul&gt; &lt;li&gt;Docker&lt;/li&gt; &lt;li&gt;Docker Compose&lt;/li&gt; &lt;li&gt;AWS CLI&lt;/li&gt; &lt;li&gt;Golang&lt;/li&gt; &lt;/ul&gt; &lt;h2 id=&quot;setting-up-your-environment&quot;&gt;Setting Up...</description>
        <pubDate>Tue, 02 Jul 2024 00:00:00 +0000</pubDate>
        <link>https://codewizardly.com/test-lambdas-with-docker/</link>
        <guid isPermaLink="true">https://codewizardly.com/test-lambdas-with-docker/</guid>
        
        <category>aws</category>
        
        <category>docker</category>
        
        <category>lambda</category>
        
        <category>golang</category>
        
        <category>devops</category>
      </item>
    
      <item>
        <title>Kubent: A Tool to Detect Deprecated APIs in Kubernetes</title>
        <description>&lt;p&gt;Welcome to an exploration of Kubent, an invaluable tool in the realm of Kubernetes. In this blog post, we will delve into the capabilities of Kubent and its role in simplifying the management of Kubernetes clusters. Whether you are a seasoned developer or a curious newcomer, join us on this informative journey as we uncover the benefits and features of Kubent.&lt;/p&gt; &lt;h2 id=&quot;an-introduction-to-kubent&quot;&gt;An Introduction to Kubent&lt;/h2&gt; &lt;p&gt;&lt;a href=&quot;https://github.com/doitintl/kube-no-trouble&quot;&gt;Kubent&lt;/a&gt;, an abbreviation for “Kube No Trouble,” is a user-friendly tool designed to assist users in ensuring API version compatibility within their Kubernetes clusters. Before we explore the importance of upgrading API versions,...</description>
        <pubDate>Tue, 04 Jul 2023 00:00:00 +0000</pubDate>
        <link>https://codewizardly.com/kubent-a-tool-to-detect-deprecated-apis-in-kubernetes/</link>
        <guid isPermaLink="true">https://codewizardly.com/kubent-a-tool-to-detect-deprecated-apis-in-kubernetes/</guid>
        
        <category>kubernetes</category>
        
        <category>devops</category>
      </item>
    
      <item>
        <title>Configure Multi Git Accounts On Linux</title>
        <description>&lt;p&gt;Managing multiple user accounts can be a challenging task. A simple use-case scenario is to have an account for a job, and a separate account for personal purposes. Jumping back and forth between these accounts can be a pain, and you are prone to forget which account you are using and causing a lot of confusion. In general, it is recommended to use a single account for all your work, according to &lt;a href=&quot;(https://docs.github.com/en/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts)&quot;&gt;GitHub&lt;/a&gt;. But when it is not possible, you can have separate directories to host your git repositories for each account, so that you can easily switch between...</description>
        <pubDate>Tue, 05 Jul 2022 00:00:00 +0000</pubDate>
        <link>https://codewizardly.com/configure-multi-git-accounts-on-linux/</link>
        <guid isPermaLink="true">https://codewizardly.com/configure-multi-git-accounts-on-linux/</guid>
        
        <category>devops</category>
        
        <category>devops</category>
      </item>
    
      <item>
        <title>What Is Terraform Drift And How To Avoid It?</title>
        <description>&lt;blockquote&gt; &lt;p&gt;Drift is the term for when the real-world state of your infrastructure differs from the state defined in your configuration&lt;/p&gt; &lt;/blockquote&gt; &lt;p&gt;Have you ever been about to finish washing the dishes and suddenly someone puts a dirty glass and some pots of the last meal in front of you? Then you have to clean the glass and the pots, and then the scene repeats itself over and over again. Solving Terraform drifts is like washing a huge pile of dishes that never ends. In a real environment at any scale mitigate drifts is not an easy task.&lt;/p&gt; &lt;p&gt;Let’s take...</description>
        <pubDate>Tue, 24 Aug 2021 00:00:00 +0000</pubDate>
        <link>https://codewizardly.com/how-to-avoid-terraform-drifts/</link>
        <guid isPermaLink="true">https://codewizardly.com/how-to-avoid-terraform-drifts/</guid>
        
        <category>iac</category>
        
        <category>devops</category>
      </item>
    
      <item>
        <title>How To Deploy to AWS ECS Using The Same Docker Tag With Terraform</title>
        <description>&lt;p&gt;Most of us have heard about &lt;a href=&quot;https://www.terraform.io&quot;&gt;Terraform&lt;/a&gt; and &lt;a href=&quot;https://aws.amazon.com/ecs&quot;&gt;AWS ECS&lt;/a&gt;. One of the situations in which I have found myself using both is not being able to deploy the latest changes when using the same docker tag. The pipeline builds a new docker image with no errors but when applying the changes with Terraform it literally does nothing even though a new docker image is ready. Terraform won’t recognize a change because the same docker tag is being used. Terraform only makes changes to the infrastructure if needed, for this, it compares the infrastructure described in a &lt;a...</description>
        <pubDate>Fri, 05 Mar 2021 00:00:00 +0000</pubDate>
        <link>https://codewizardly.com/how-to-deploy-to-aws-ecs-using-the-same-docker-tag-with-terraform/</link>
        <guid isPermaLink="true">https://codewizardly.com/how-to-deploy-to-aws-ecs-using-the-same-docker-tag-with-terraform/</guid>
        
        <category>devops</category>
        
        <category>aws</category>
        
        <category>devops</category>
      </item>
    
      <item>
        <title>Schedule Smoke Tests Run With GitLab API</title>
        <description>&lt;p&gt;A &lt;a href=&quot;https://softwaretestingfundamentals.com/smoke-testing&quot;&gt;Smoke test&lt;/a&gt; is a type of software testing that comprises of a non-exhaustive set of tests that aim at ensuring that the most important functions work. Ideally, smoke tests should be triggered after a deployment is complete and the cache not interfere with the process.&lt;/p&gt; &lt;p&gt;The main idea is to run smoke tests after a pipeline deployment has been carried out in order to make sure it came out as expected. Waiting a certain amount of time after the event can be complex if you want to do it with a responsible use of resources. The easiest approach...</description>
        <pubDate>Fri, 29 Jan 2021 00:00:00 +0000</pubDate>
        <link>https://codewizardly.com/schedule-smoke-test-on-gitlab/</link>
        <guid isPermaLink="true">https://codewizardly.com/schedule-smoke-test-on-gitlab/</guid>
        
        <category>devops</category>
        
        <category>devops</category>
      </item>
    
      <item>
        <title>Join to the Hacktoberfest 2020 Celebration</title>
        <description>&lt;blockquote&gt; &lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt; This post covers Hacktoberfest 2020. For current event information, visit &lt;a href=&quot;https://hacktoberfest.com&quot;&gt;hacktoberfest.com&lt;/a&gt;.&lt;/p&gt; &lt;/blockquote&gt; &lt;p&gt;Hacktoberfest is a celebration sponsored by &lt;a href=&quot;https://www.digitalocean.com/&quot;&gt;Digital Ocean&lt;/a&gt;, &lt;a href=&quot;https://www.intel.in&quot;&gt;intel&lt;/a&gt; and &lt;a href=&quot;https://dev.to/&quot;&gt;Dev&lt;/a&gt; that consist in contributing to open source projects on GitHub. Contributing is very beneficial because it helps you to develop your skills at the same time you help others, building your confidence as a developer, it gives you a nice resume and also the opportunity to meet new and talented people. If you want to know more details about Hacktoberfest 2020, you can check the &lt;a href=&quot;https://hacktoberfest.digitalocean.com/details&quot;&gt;official site&lt;/a&gt; for this event.&lt;/p&gt;...</description>
        <pubDate>Thu, 01 Oct 2020 00:00:00 +0000</pubDate>
        <link>https://codewizardly.com/hacktoberfest-2020/</link>
        <guid isPermaLink="true">https://codewizardly.com/hacktoberfest-2020/</guid>
        
        <category>code</category>
        
        <category>code</category>
      </item>
    
      <item>
        <title>Prometheus Alertmanager Sending Emails</title>
        <description>&lt;p&gt;Let’s recap, we have a Prometheus instance on an AWS EC2 instance configured to discover services on port 9100 in the same network and one Node Exporter instance collecting OS metrics that can be easily upgraded to many Node Exporter instances as desired.&lt;/p&gt; &lt;p&gt;Follow the whole history:&lt;/p&gt; &lt;ul&gt; &lt;li&gt;&lt;a href=&quot;https://codewizardly.com/prometheus-on-aws-ec2-part1&quot;&gt;Install Prometheus on AWS EC2&lt;/a&gt;&lt;/li&gt; &lt;li&gt;&lt;a href=&quot;https://codewizardly.com/prometheus-on-aws-ec2-part2&quot;&gt;Prometheus Node Exporter on AWS EC2&lt;/a&gt;&lt;/li&gt; &lt;li&gt;&lt;a href=&quot;https://codewizardly.com/prometheus-on-aws-ec2-part3&quot;&gt;Prometheus Discovery Service on AWS EC2&lt;/a&gt;&lt;/li&gt; &lt;li&gt;Prometheus Alertmanager Sending Emails&lt;/li&gt; &lt;/ul&gt; &lt;p&gt;But we are not done yet, we don’t want to be monitoring by ourselves. Prometheus can send us an alert to an email when it finds something....</description>
        <pubDate>Wed, 01 Jul 2020 00:00:00 +0000</pubDate>
        <link>https://codewizardly.com/prometheus-on-aws-ec2-part4/</link>
        <guid isPermaLink="true">https://codewizardly.com/prometheus-on-aws-ec2-part4/</guid>
        
        <category>monitoring</category>
        
        <category>devops</category>
      </item>
    
      <item>
        <title>Prometheus Service Discovery on AWS EC2</title>
        <description>&lt;p&gt;Follow the complete story:&lt;/p&gt; &lt;ul&gt; &lt;li&gt;&lt;a href=&quot;https://codewizardly.com/prometheus-on-aws-ec2-part1&quot;&gt;Install Prometheus on AWS EC2&lt;/a&gt;&lt;/li&gt; &lt;li&gt;&lt;a href=&quot;https://codewizardly.com/prometheus-on-aws-ec2-part2&quot;&gt;Prometheus Node Exporter on AWS EC2&lt;/a&gt;&lt;/li&gt; &lt;li&gt;Prometheus Discovery Service on AWS EC2&lt;/li&gt; &lt;li&gt;&lt;a href=&quot;https://codewizardly.com/prometheus-on-aws-ec2-part4&quot;&gt;Prometheus Alertmanager Sending Emails&lt;/a&gt;&lt;/li&gt; &lt;/ul&gt; &lt;p&gt;Cool, now you have Prometheus and Node Exporter up and running. What if you want to add a third EC2 instance? A trivial task, you only need to go back to Prometheus, update its static configuration and restart the service, manually. So, every time some change is needed, you might need to do it yourself or hire Bob &lt;del&gt;if your name is Bob, don’t take it personal.&lt;/del&gt; to work on...</description>
        <pubDate>Tue, 30 Jun 2020 00:00:00 +0000</pubDate>
        <link>https://codewizardly.com/prometheus-on-aws-ec2-part3/</link>
        <guid isPermaLink="true">https://codewizardly.com/prometheus-on-aws-ec2-part3/</guid>
        
        <category>monitoring</category>
        
        <category>devops</category>
      </item>
    
      <item>
        <title>Prometheus Node Exporter on AWS EC2</title>
        <description>&lt;p&gt;In the &lt;a href=&quot;https://codewizardly.com/prometheus-on-aws-ec2-part1&quot;&gt;previous topic&lt;/a&gt; we installed Prometheus and now is ready to receive metrics. The next step is to launch a second AWS EC2 instance, install Prometheus Node Exporter in it and finally, configure Prometheus to collect its metrics.&lt;/p&gt; &lt;p&gt;To continue reading follow these links:&lt;/p&gt; &lt;ul&gt; &lt;li&gt;&lt;a href=&quot;https://codewizardly.com/prometheus-on-aws-ec2-part1&quot;&gt;Install Prometheus on AWS EC2&lt;/a&gt;&lt;/li&gt; &lt;li&gt;Prometheus Node Exporter on AWS EC2&lt;/li&gt; &lt;li&gt;&lt;a href=&quot;https://codewizardly.com/prometheus-on-aws-ec2-part3&quot;&gt;Prometheus Discovery Service on AWS EC2&lt;/a&gt;&lt;/li&gt; &lt;li&gt;&lt;a href=&quot;https://codewizardly.com/prometheus-on-aws-ec2-part4&quot;&gt;Prometheus Alertmanager Sending Emails&lt;/a&gt;&lt;/li&gt; &lt;/ul&gt; &lt;h1 id=&quot;prometheus-node-exporter&quot;&gt;Prometheus Node Exporter&lt;/h1&gt; &lt;p&gt;There are many &lt;a href=&quot;https://prometheus.io/docs/instrumenting/exporters&quot;&gt;exporters and integrations&lt;/a&gt; available for Prometheus. As mentioned above, in this example we are going to install Prometheus Node Exporter...</description>
        <pubDate>Sun, 28 Jun 2020 00:00:00 +0000</pubDate>
        <link>https://codewizardly.com/prometheus-on-aws-ec2-part2/</link>
        <guid isPermaLink="true">https://codewizardly.com/prometheus-on-aws-ec2-part2/</guid>
        
        <category>monitoring</category>
        
        <category>devops</category>
      </item>
    
      <item>
        <title>Install Prometheus on AWS EC2</title>
        <description>&lt;p&gt;Let’s face it, there will be something wrong at some point, and you need to know when it is happening. That awesome application you have been working on for 6 months and you treat as your child is going to be in trouble someday. Therefore, how to be there exactly when something needs to be fixed? How do you tell that something is crashing? Obviously, it is not possible for us to be there all the time, so we need something else do that for us. &lt;a href=&quot;https://prometheus.io&quot;&gt;Prometheus&lt;/a&gt; is an awesome open-source tool for monitoring, designed for reliability, and meant...</description>
        <pubDate>Sun, 14 Jun 2020 00:00:00 +0000</pubDate>
        <link>https://codewizardly.com/prometheus-on-aws-ec2-part1/</link>
        <guid isPermaLink="true">https://codewizardly.com/prometheus-on-aws-ec2-part1/</guid>
        
        <category>monitoring</category>
        
        <category>devops</category>
      </item>
    
      <item>
        <title>Mutation Testing with Stryker and Docker</title>
        <description>&lt;p&gt;How do we know that we are writing quality code? Mostly we rely on unit tests or integration tests to answer that question. But then, the question repeats itself. How do we know that we are writing good tests? Let me introduce you Stryker, it allows you to test your tests with mutation testing. Stryker guys have a complete explanation and got mostly everything covered on &lt;a href=&quot;https://stryker-mutator.io/&quot;&gt;their official site&lt;/a&gt; which you should visit.&lt;/p&gt; &lt;p&gt;Following an approach with &lt;a href=&quot;https://www.docker.com/&quot;&gt;Docker&lt;/a&gt;, I found it easier to implement in old projects since it is not necessary to upgrade libraries or care about...</description>
        <pubDate>Fri, 24 Jan 2020 00:00:00 +0000</pubDate>
        <link>https://codewizardly.com/mutation-testing-with-stryker-and-docker/</link>
        <guid isPermaLink="true">https://codewizardly.com/mutation-testing-with-stryker-and-docker/</guid>
        
        <category>test</category>
        
        <category>devops</category>
      </item>
    
  </channel>
</rss>
