<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Consul on The IT Hollow</title>
    <link>https://theithollow.com/tags/consul/</link>
    <description>Recent content in Consul on The IT Hollow</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 21 May 2018 14:05:16 +0000</lastBuildDate>
    <atom:link href="https://theithollow.com/tags/consul/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Using Hashicorp Consul to Store Terraform State</title>
      <link>https://theithollow.com/2018/05/21/using-hashicorp-consul-to-store-terraform-state/</link>
      <pubDate>Mon, 21 May 2018 14:05:16 +0000</pubDate>
      <guid>https://theithollow.com/2018/05/21/using-hashicorp-consul-to-store-terraform-state/</guid>
      <description>&lt;p&gt;Hashicorp&amp;rsquo;s Terraform product is very popular in describing your infrastructure as code. One thing that you need consider when using Terraform is where you&amp;rsquo;ll store your state files and how they&amp;rsquo;ll be locked so that two team members or build servers aren&amp;rsquo;t stepping on each other. State can be stored in &lt;a href=&#34;https://www.terraform.io/&#34;&gt;Terraform Enterprise (TFE)&lt;/a&gt; or with some cloud services such as S3. But if you want to store your state, within your data center, perhaps you should check out &lt;a href=&#34;https://www.hashicorp.com/&#34;&gt;Hashicorp&amp;rsquo;s&lt;/a&gt; Consul product.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
