The OneFuse Property Toolkit is the Swiss army knife of the OneFuse Platform.
It can be used in many different ways to assist you in meeting your automation needs. It can be used to simplify configurations, define business logic as configuration, build simple logic or tackle the most complex problems. In its simplest form its meta-data that can be used as a reference offering simple name value pairs that can be used as a reference for decision making. In its most powerful form it can contain logic, decision trees, platform abstractions, and much more.
Property Toolkit can be leveraged to provide basic groupings of properties allowing you to call upon them to access properties and values they hold. This can be done natively on most platforms however when used within the capabilities of a particular platform the data is restricted to that platform and would need to be duplicated for each platform you use.
OneFuse Property Sets are used to create and maintain data used as part of the Property Toolkit. These property sets leverage standard JSON and can be dynamic using our Template Engine, giving you the power to determine how they should be structured, across platforms or tools.
Property Toolkit can be leveraged alongside native vRealize Automation features such as Blueprint Expressions, Property Groups (inputs and constants), delivering enhanced dynamic capabilities. OneFuse Property Sets can be dynamically computed, nested, leveraged in multiple Cloud Assembly machine lifecycles or on the canvas for dynamic creation or reference to existing property sets, across blueprints, projects, tenants vRA instances or even simultaneously between vRA, Terrform and other tools. With Property Toolkit it’s possible to dynamically create tags or entire sets of properties with nested structures to efficiently drive standards and reduce blueprint complexity.
Property Toolkit can be leveraged to drive dynamic configuration of any Terraform provider or module. OneFuse Property Sets can be computed, nested and easily leveraged across multiple Terraform configurations. With Property Toolkit it’s possible to dynamically create tags or entire sets of properties with nested structures to efficiently drive standards and reduce configuration complexity, accomplishing scenarios ranging from normalizing sizing for VM deployments across clouds to dynamically assigning and deploying environment-specific configurations.
OneFuse Property Toolkit with Terraform
Drive variable/property and/or tag assignment dynamically
On Terraform or vRealize Automation using OneFuse Property Sets
Create new properties in vRA or variables in Terraform
Dynamically create custom properties/tags/variables in vRA and Terraform with support for rendering both the key and value via Template Engine
Support for multiple and nested Property Sets
Along with ordering when multiple are defined
Features and Capabilities
Logically separate out global properties from properties specific to an upstream platform, e.g. vRA, Terraform and/or CloudBolt.
- Deliver multiple automation scenarios with minimal overhead via OneFuse Template Engine, can be combined with dynamic OneFuse Policies
- Ability to assign a Static Property Set from a property definition in order to drive a set of (dynamic) properties from a single request field
- Can be used interchangeably between vRA7, vRA8 and Terraform
- Delivers dozens to thousands of automation scenarios with minimal overhead via dynamic templated configurations, avoiding complexity and sprawl
- Define properties/tags/variables via rich JSON format, beyond simple key:value pairs, fully templatable
- Supports nested Property Sets (3 levels)
- Supports ordering sets/groupings of properties
- Can be leveraged and combined with vRA features such as blueprint expressions, tags, properties, property groups (inputs and constants)
- Can be used across blueprints, projects, tenants and instances of vRA
- Migration support for vRA property groups to OneFuse Property Sets
- Cloud Assembly Cloud Template Canvas support allows for dragging in a Property Set component to dynamically create or reference an existing property set in order to drive vRA components/variables
- Reduces the complexity of blueprints, reducing the need for complex blueprint expressions and external workflows for custom business logic
- Ability to dynamically assign variables and apply to any property or tag for any provider
- Allows for abstracting decisioning/scenarios and custom logic to reduce the need for complex HCL or Go-based custom code
- Included Terraform provider and reference modules to get started quickly
- Support for Terraform open source, cloud and enteprise