<?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 Robert Terakedis</title>
    <link>https://blog.terakedis.dev/tags/automation/</link>
    <description>Recent content in Automation on Robert Terakedis</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>Copyright © 2020 Robert Terakedis; all rights reserved.</copyright>
    <lastBuildDate>Sat, 18 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.terakedis.dev/tags/automation/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The $300K Spreadsheet: How Manual Provisioning Became a Liability</title>
      <link>https://blog.terakedis.dev/post/the-300k-spreadsheet/</link>
      <pubDate>Sat, 18 Apr 2026 00:00:00 +0000</pubDate>
      
      <guid>https://blog.terakedis.dev/post/the-300k-spreadsheet/</guid>
      <description>
        
          
            &lt;p&gt;Last year I got pulled into a project where the team was drowning in spreadsheets. Not the good kind, but rather the unfortunate kind: manual user provisioning lists, copy-paste operations between systems, and a recurring cloud bill that kept climbing because of over-provisioned resources sitting idle.&lt;/p&gt;
&lt;p&gt;The kicker? Along with all the manual inefficiences, we incurred $300,000/year in overprovisioned cloud spend. And that was before we even talked about the staff time or the risk of things breaking when a step in the process was missed.&lt;/p&gt;
          
          
        
      </description>
    </item>
    
    <item>
      <title>Postman Pre-Request Script for Docebo API</title>
      <link>https://blog.terakedis.dev/post/postman-pre-request-script-for-docebo-api/</link>
      <pubDate>Wed, 22 Jan 2025 00:00:00 +0000</pubDate>
      
      <guid>https://blog.terakedis.dev/post/postman-pre-request-script-for-docebo-api/</guid>
      <description>
        
          
            &lt;p&gt;I&#39;ve recently been involved with a project at work to modernize the processes around Docebo, our Learning Management System (LMS). A significant portion of this project involves workflow automation and passing data/events between multiple systems. We accomplish this automation using webhooks and a number of API calls (which you can view at &lt;a href=&#34;https://doceboapi.docebosaas.com/api-browser/&#34;&gt;Docebo&#39;s API Browser&lt;/a&gt;).  Early in the process, I stumbled onto the Docebo Community post about &lt;a href=&#34;https://community.docebo.com/integrations-apis-45/after-the-community-coaching-session-using-postman-9897&#34;&gt;Using Postman&lt;/a&gt; (and the on-demand &lt;a href=&#34;https://community.docebo.com/events/on-demand-community-coaching-session-using-postman-with-the-api-97&#34;&gt;Community Coaching Session&lt;/a&gt;) which contained a downloadable Postman API collection.  This was a GREAT starting point, but the collection used an interactive login to get oAuth2 tokens. I wanted to automate the authentication process and avoid the interactive logins when I was testing against our sandbox LMS instance.&lt;/p&gt;
          
          
        
      </description>
    </item>
    
    <item>
      <title>Updated GitHub Actions to Publish Hugo Site From Private to Public Repo</title>
      <link>https://blog.terakedis.dev/post/updated-github-actions-publish-private-hugo-repo-to-public-pages-site/</link>
      <pubDate>Tue, 27 Oct 2020 00:00:00 +0000</pubDate>
      
      <guid>https://blog.terakedis.dev/post/updated-github-actions-publish-private-hugo-repo-to-public-pages-site/</guid>
      <description>
        
          
            &lt;p&gt;When I restarted my blogging journey last year, I went with Hugo to generate a static website hosted as a GitHub Pages site.  As mentioned, Blogger and WordPress always suffered recurring problems, and maintenance with WordPress still turned into a time suck due to its complexity.  By comparison, GitHub has been a nearly painless hosting provider, and the way I&#39;ve configured it has allowed me to keep drafts hidden by staging in a private repository.&lt;/p&gt;
          
          
        
      </description>
    </item>
    
    <item>
      <title>Using GitHub Actions to Publish Hugo Site From Private to Public Repo</title>
      <link>https://blog.terakedis.dev/post/github-actions-publish-private-hugo-repo-to-public-pages-site/</link>
      <pubDate>Fri, 14 Aug 2020 00:00:00 +0000</pubDate>
      
      <guid>https://blog.terakedis.dev/post/github-actions-publish-private-hugo-repo-to-public-pages-site/</guid>
      <description>
        
          
            &lt;p&gt;I restarted my blogging journey earlier this year when I started looking into &lt;del&gt;Jekyll&lt;/del&gt; Hugo to generate a static website.  I had past experience with Blogger and Wordpress, but frankly had periodic problems with both platforms that ended up being a time suck.  As it has been, Hugo has been a simplistic publishing method and GitHub a reliable (and FREE) hosting provider.  Yet, my desire to keep my drafts private (.e.g the use of 2 separate repositories) has created a small overhead in that I have to build and manually commit the website changes to the public repository to make them live.&lt;/p&gt;
          
          
        
      </description>
    </item>
    
    <item>
      <title>Another GitHub Actions Update - Using Deploy Keys Instead Of Personal Access Tokens</title>
      <link>https://blog.terakedis.dev/post/another-github-actions-update-change-hugo-publish-deploy-keys/</link>
      <pubDate>Fri, 06 Mar 2020 00:00:00 +0000</pubDate>
      
      <guid>https://blog.terakedis.dev/post/another-github-actions-update-change-hugo-publish-deploy-keys/</guid>
      <description>
        
          
            &lt;p&gt;When I restarted my blogging journey in 2020, I switched from Jekyll to Hugo hosted in GitHub pages.  It&#39;s been a relatively painless journey, and kudos to GitHub as a rock-solid hosting provider.  I&#39;ve covered it before (&lt;a href=&#34;https://blog.terakedis.dev/post/github-actions-publish-private-hugo-repo-to-public-pages-site/&#34;&gt;Initial Setup&lt;/a&gt; and &lt;a href=&#34;https://blog.terakedis.dev/post/updated-github-actions-publish-private-hugo-repo-to-public-pages-site/&#34;&gt;First Update&lt;/a&gt;), but I&#39;ve been incredibly happy with private-to-public publishing workflow that allows me to keep drafts and work-in-progress hidden.  That said, a recent comment gave me reason to make another update to the Workflow.   Read on for more detail...&lt;/p&gt;
          
          
        
      </description>
    </item>
    
  </channel>
</rss>