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
OneFuse IPAM policies have some special qualities that make managing IPAM integrations very easy, flexible, and portable. IPAM policies in OneFuse define the network or networks they represent abstracted from the actual IPAM provider. This offers many benefits over network definitions that are tightly tied to a specific provider. This
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
