<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Terraform on iAutomate</title>
    <link>/tags/terraform/</link>
    <description>Recent content in Terraform on iAutomate</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Thu, 27 Oct 2022 00:00:00 +0000</lastBuildDate><atom:link href="/tags/terraform/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Untapping Infrastructure Registry in GitLab – Part 1</title>
      <link>/blog/untapping-infrastructure-registry-in-gitlab-part-1/</link>
      <pubDate>Thu, 27 Oct 2022 00:00:00 +0000</pubDate>
      
      <guid>/blog/untapping-infrastructure-registry-in-gitlab-part-1/</guid>
      <description>Introduction Yesterday I spent a few hours in Infrastructure Registry for my learning. Oh, well, I am not impressed with the implementation work. But I still love the feature. So, here is the blog post to get started.
Prerequisites  Azure Account.  Refer here for free access (12 Months)   GitLab Account.  Set up your own GitLab instance    Requirement  Create a Terraform module Publish to Infrastructure Registry Consume the module to create Azure resources  Solution  Note: For now, let us ignore the quality of the project scaffolding, security, code scanning, process, and protocols.</description>
    </item>
    
  </channel>
</rss>
