<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Automation on melastmohican.github.io</title>
		<link>https://melastmohican.github.io/tags/automation/</link>
		<description>Recent content in Automation on melastmohican.github.io</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Sat, 21 Mar 2020 12:36:30 -0700</lastBuildDate>
		
			<atom:link href="https://melastmohican.github.io/tags/automation/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Terraform Best Practice Guide for Developers</title>
				<link>https://melastmohican.github.io/posts/terraform_best_practice_guide_for_developers/</link>
				<pubDate>Sat, 21 Mar 2020 12:36:30 -0700</pubDate>
				<guid>https://melastmohican.github.io/posts/terraform_best_practice_guide_for_developers/</guid>
				<description>&lt;p&gt;&lt;a href=&#34;https://www.terraform.io/&#34;  class=&#34;external-link&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;Terraform&lt;/a&gt; is an open-source infrastructure as code software tool created by HashiCorp. It enables users to define and provision infrastructure using a high-level configuration language known as Hashicorp Configuration Language (HCL), or optionally JSON. Terraform is platform-agnostic; you can use it to manage bare metal servers or cloud servers like AWS, Google Cloud Platform, OpenStack, and Azure. Terraform enables you to safely and predictably create, change, and improve infrastructure. It is an open-source tool that codifies APIs into declarative configuration files that can be shared amongst team members, treated as code, edited, reviewed, and versioned.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Maven Archetypes Project Templating</title>
				<link>https://melastmohican.github.io/posts/maven-archetypes-project-templating/</link>
				<pubDate>Fri, 06 Mar 2020 09:50:53 -0800</pubDate>
				<guid>https://melastmohican.github.io/posts/maven-archetypes-project-templating/</guid>
				<description>&lt;h2 id=&#34;intro&#34;&gt;&#xA;  Intro&#xA;  &lt;a class=&#34;heading-link&#34; href=&#34;#intro&#34;&gt;&#xA;    &lt;i class=&#34;fa-solid fa-link&#34; aria-hidden=&#34;true&#34; title=&#34;Link to heading&#34;&gt;&lt;/i&gt;&#xA;    &lt;span class=&#34;sr-only&#34;&gt;Link to heading&lt;/span&gt;&#xA;  &lt;/a&gt;&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;I am developer and I like &lt;a href=&#34;https://en.wikipedia.org/wiki/Don%27t_repeat_yourself&#34;  class=&#34;external-link&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;DRY&lt;/a&gt;. If there is any task you have to do more than once you should probably automate it. starting a new project, it can be tedious and time-consuming to start over and over again from scratch. You can use &lt;a href=&#34;https://start.spring.io/&#34;  class=&#34;external-link&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;Spring Initializr&lt;/a&gt; to boostrap your new application or even better without leaving the shell &lt;a href=&#34;https://docs.spring.io/spring-boot/docs/current/reference/htmlsingle/#cli-init&#34;  class=&#34;external-link&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;Spring Boot CLI&lt;/a&gt;.  You will get nice clean project with the latest versions of dependencies but what if you need to use specific internal libraries or configuration files? Wouldn&amp;rsquo;t be nice to have project template and generate new one by answersing few simple questions? Project generation (scaffolding) was made popular by the Ruby on Rails framework and now we got many generators included in popular frameworks or standalone but if you are already using Maven as you your build tool don&amp;rsquo;t look any further.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Migrating existing AWS infrastructure to new acount</title>
				<link>https://melastmohican.github.io/posts/aws-resource-migration/</link>
				<pubDate>Thu, 05 Mar 2020 13:37:39 -0800</pubDate>
				<guid>https://melastmohican.github.io/posts/aws-resource-migration/</guid>
				<description>&lt;h1 id=&#34;scenario&#34;&gt;&#xA;  Scenario&#xA;  &lt;a class=&#34;heading-link&#34; href=&#34;#scenario&#34;&gt;&#xA;    &lt;i class=&#34;fa-solid fa-link&#34; aria-hidden=&#34;true&#34; title=&#34;Link to heading&#34;&gt;&lt;/i&gt;&#xA;    &lt;span class=&#34;sr-only&#34;&gt;Link to heading&lt;/span&gt;&#xA;  &lt;/a&gt;&#xA;&lt;/h1&gt;&#xA;&lt;p&gt;We want to migrate hundreds of AWS resources to a new account. Up to now, all resources were created manually using AWS Console or CLI tool.&lt;/p&gt;&#xA;&lt;h2 id=&#34;cloudformation&#34;&gt;&#xA;  CloudFormation&#xA;  &lt;a class=&#34;heading-link&#34; href=&#34;#cloudformation&#34;&gt;&#xA;    &lt;i class=&#34;fa-solid fa-link&#34; aria-hidden=&#34;true&#34; title=&#34;Link to heading&#34;&gt;&lt;/i&gt;&#xA;    &lt;span class=&#34;sr-only&#34;&gt;Link to heading&lt;/span&gt;&#xA;  &lt;/a&gt;&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;CloudFormation is the inhouse cloud provisioning tool of AWS for declaratively describing your cloud resources.&lt;/p&gt;&#xA;&lt;p&gt;CloudFormation is a hard, complex, inconsistent and badly documented piece of software. A stack is an atomic collection of resources in CloudFormation. Its creation or update succeeds only and only if all the resources within the stack succeed. A failure within a stack update leads to a rollback back to the previous state.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
