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 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
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
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)
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
In this example we are going to configure a few different types of custom properties. The properties we are going to configure are: VMware.VirtualCenter.Fo
