Namespace No Longer Required When Specifying associable_types When Creating a Tagging Category To Be Used For a Tag Based Storage Policy

Products

• VMware vCenter Server

Issue/Introduction

When making an API call to create a tagging category the associable_types list of valid types that the category applies to required the VIM namespace be prefixed to the type for Storage Policy to understand the categories tags.

Ex: POST api/cis/tagging/category

Request Body:

{
    "name": "TheOldWayOfSpecifyingAssociableTypes",
    "description": "",
    "cardinality": "SINGLE",
    "associable_types": [
        "urn:vim25:Datastore"
    ]
}

 

However, when querying information about the tag category, the VIM namespace is not prefixed to the associable_types.

Ex: GET api/cis/tagging/category/{categoryId}

Request Body:

{
    "id": {categoryId}
    "name": "TheOldWayOfSpecifyingAssociableTypes",
    "description": "",
    "cardinality": "SINGLE",
    "associable_types": [
        "Datastore"
    ]
}


This can unfortunately, make the automation around working with tags and tag categories difficult.

Environment

VMware vCenter Server 8.x

Resolution

A product fix has been developed such that the VIM namespace is no longer required.

Ex: POST: api/cis/tagging/category

Request Body:

{
    "name": "TheNewWayOfSpecifyingAssociableTypes",
    "description": "",
    "cardinality": "SINGLE",
    "associable_types": [
        "Datastore"
    ]
}

The fix will be made available in a future release of the product.