InlineNsxPolicyResource1

InlineNsxPolicyResource1
InlineNsxPolicyResource1
JSON Example
{
    "origin_site_id": "string",
    "owner_id": "string",
    "parent_path": "string",
    "path": "string",
    "realization_id": "string",
    "relative_path": "string",
    "remote_path": "string",
    "unique_id": "string"
}
string
origin_site_id
Optional

This is a UUID generated by the system for knowing which site owns an object. This is used in NSX+.

string
owner_id
Optional

This is a UUID generated by the system for knowing who owns this object. This is used in NSX+.

string
parent_path
Optional

Path of its parent

string
path
Optional

Absolute path of this object

string
realization_id
Optional

This is a UUID generated by the system for realizing the entity object. In most cases this should be same as 'unique_id' of the entity. However, in some cases this can be different because of entities have migrated their unique identifier to NSX Policy intent objects later in the timeline and did not use unique_id for realization. Realization id is helpful for users to debug data path to correlate the configuration with corresponding intent.

string
relative_path
Optional

Path relative from its parent

string
remote_path
Optional

This path is populated only in case of multi-site scenario. Currently it is supported only for LM objects. When LM is onboarded to multi-site platform like NAPP or GM, remote_path will be set to the globally unique path across multi-site topology . It is generated based on local site-name and uses /org tree namespace. Note: It is populated only for LM objects. Not supported on the GM.

string
unique_id
Optional

This is a UUID generated by the GM/LM to uniquely identify entities in a federated environment. For entities that are stretched across multiple sites, the same ID will be used on all the stretched sites.