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 a machine record within an Active Directory OU 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 Active Directory policy 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
In this article we are going to walk through using OneFuse to reserve an IP address 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 IPAM policy we created as part of
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 create a vRA8 blueprint that uses the OneFuse Active Directory module to provide AD integration for provisioned workloads. We will use the Active Directory (AD) policy that we created in the “Creating a OneFuse Active Directory Policy” article. I will also be leveraging
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
The OneFuse Active Directory (AD) module offers features for placing deployed computer objects into the appropriate Active Directory (AD) organizational units (OU). This includes support for pre-build organization units (OU), final Organizational Unit placement, as well as placement of computer objects into Active Directory (AD) security groups. Active Directory (AD)
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
In this article, we are going to create a vRA8 blueprint that uses the OneFuse IPAM module to provide IPAM integration for provisioned workloads. We won’t just be supplying IP information to vRA8 in this example, OneFuse will determine the network placement as well. We will have a future
