Editor's note (2026): The methodology described in this post is what I now call Decisions as Code. Property Toolkit was the OneFuse implementation of the same idea. See "Decisions as Code" for the current framing. In previous articles, I covered using the OneFuse Foundations Modules (Naming,
Editor's note (2026): The methodology described in this post is what I now call Decisions as Code. Property Toolkit was the OneFuse implementation of the same idea. See "Decisions as Code" for the current framing. In my previous articles, we looked at consuming the OneFuse Modules
In previous articles, I walked through how to use OneFuse Naming, IPAM, DNS, and Active Directory individually within a Terraform configuration. In this article, we are going to put them all together into one single Terraform configuration to provide access to all resources. By the end of this article, we
In this article we are going to walk through using OneFuse to create DNS records within a Terraform configuration. To do this we will create a new Terraform configuration that uses the OneFuse provider data source and resource for the DNS policy we created as part of “Creating a OneFuse
Editor's note (2026): The methodology described in this post is what I now call Decisions as Code. Property Toolkit was the OneFuse implementation of the same idea. See "Decisions as Code" for the current framing. If you have read some of my other articles you have
In this article we are going to add OneFuse DNS support to a vRA8 blueprint. If you have been following my previous articles you probably have an idea of how this is going to work. We are going to build upon the examples from previous articles by leveraging the same
Automating the creation of DNS records is becoming increasingly more important in the enterprise. One bad record or typo can cause outages or mission critical services. In this article, I’m going to walk through creating a DNS Policy in OneFuse using Infoblox as a DNS provider. OneFuse DNS Features
Editor's note (2026): The methodology described in this post is what I now call Decisions as Code. Property Toolkit was the OneFuse implementation of the same idea. See "Decisions as Code" for the current framing. Introduction The OneFuse Extensibility Management Platform accelerates vRealize Automation 8 (vRA8)
Editor's note (2026): The methodology described in this post is what I now call Decisions as Code. Property Toolkit was the OneFuse implementation of the same idea. See "Decisions as Code" for the current framing. Introduction This post will build upon the prior post, Introducing OneFuse
