vCAC Custom Properties Order of Precedence

If you’ve used the vCAC Interface from an administrative perspective, you’ll have noticed that Custom Properties can be appended in a number of areas. This gives you a great deal of flexibility in as much as you can define that every workload deployed:

  • by a Business Group
  • from a Blueprint
  • to a Reservation
  • against a Compute Resource
  • for a specific Endpoint

will inherit a specific set of Custom Properties which get appended at the Building Machine workflow state.

That’s all well and good, but what happens if two properties are in conflict? Which ones take precedence? The following table outlines the order in which they are received, and whether or not they can be exposed to the requestor/consumer for manipulation or input.

Precedence

Happy vCAC-ing!