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 generate a name for use in a Terraform configuration. To do this we will create a new Terraform configuration that uses the OneFuse provider data source and resource for the naming policy we created as part of Creating
In this article we are going to walk through using OneFuse to name a deployed machine in vRA8. To do this we will create a new blueprint within vRA8 and call upon the OneFuse to name it using the naming policy we created as part of “Creating a OneFuse 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. Introduction One of the things that we are often asked by
In this article, I am going to walk you through creating a Naming Policy within OneFuse. Before we begin, I want to go over why OneFuse Naming is a game changer for organizations. Many of you reading this may be thinking you don’t need an integration for naming. Read
