<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Restricted Environment on dobriak::blog</title>
    <link>https://dobriak.github.io/tags/restricted-environment/</link>
    <description>Recent content in Restricted Environment on dobriak::blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 29 Apr 2018 15:44:45 -0700</lastBuildDate>
    
	<atom:link href="https://dobriak.github.io/tags/restricted-environment/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>DC/OS Service Accounts in Restricted Environments</title>
      <link>https://dobriak.github.io/post/service-account-restricted-environment/</link>
      <pubDate>Sun, 29 Apr 2018 15:44:45 -0700</pubDate>
      
      <guid>https://dobriak.github.io/post/service-account-restricted-environment/</guid>
      <description>&lt;p&gt;We are so used to having handy little pieces of software that help us do our jobs better. If you too work in the DevOps world and write automation for infrastructure or software (or pretty much anything else) you know what I mean. Take &lt;code&gt;jq&lt;/code&gt; for an example: can you imagine writing any sort of shell script that interacts with any JSON producing API and &lt;em&gt;NOT&lt;/em&gt; using good ole trustworthy &lt;code&gt;jq&lt;/code&gt;?&lt;/p&gt;

&lt;p&gt;&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>