<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>vault on d10</title>
    <link>http://www.d10.dev/categories/vault/</link>
    <description>Recent content in vault on d10</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 24 Apr 2020 01:51:17 -0800</lastBuildDate>
    
	<atom:link href="http://www.d10.dev/categories/vault/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>HashiCorp Vault Plugin for Algorand</title>
      <link>http://www.d10.dev/blog/vault-plugin-algo/</link>
      <pubDate>Fri, 24 Apr 2020 01:51:17 -0800</pubDate>
      
      <guid>http://www.d10.dev/blog/vault-plugin-algo/</guid>
      <description>This post is based on my experience writing a plugin for HashiCorp&amp;rsquo;s Vault. While HashiCorp provides thorough documentation, I found that I had to read the code of several open-source plugins before I grokked a bigger picture of Vault plugin development. This is my attempt to document details that are not spelled out in HashiCorp&amp;rsquo;s basic example.
Vault Paths &amp;amp; Policies Paths are a key concept of Vault. It&amp;rsquo;s fundamental to understand how they work, because Vault gets its utility and flexibility largely from the path mechanism.</description>
    </item>
    
  </channel>
</rss>