In this article, we will demonstrate how to migrate Property Groups from VMware’s vRealize Automation 7 to OneFuse Property Sets. Features * Migrate vRA 7 Property Groups from user’s desired vRA tenant to OneFuse as (Static) Property Set(s). * Ability to migrate all or a selected/filtered set of
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 the “Getting Started with the OneFuse Property Toolkit” article we
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
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. The OneFuse Property Toolkit is the Swiss army knife of the
Overview This article will cover the method of creating OneFuse IPAM Policies using templated properties driven by OneFuse Static Property Sets (SPS). Considerations Simplifying the OneFuse Platform to use a single IPAM Policy is one method of calling a specified network driven by other properties from the request inputs. This
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. Leverage Property Toolkit capabilities for vRealize Automation 8 with OneFuse as
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
