/subscriptions/<platformType>/tags resource is used to store a list of system attributes available to the Subscriptions resource for the purpose of filtering systems from the resulting subscription data set.
This resource acts as a catalog of system attributes to be referenced by the tagReferences parameter in a subscription. System attributes that are not defined in a /subscriptions/<platformType>/tags resource, cannot be referenced by a Subscriptions tag filter condition. See Subscriptions for details on defining a subscription and using tag filter conditions.
The SQL to filter results employs a “STRING” comparison and not a numeric comparison on tags so you may observe inconsistent results. Tags can only be lexicographically compared.
There is a catalog for each supported <platformType>, which can only be referenced by the corresponding <platformType> subscription. For example, a container subscription (i.e. /subscriptions/containers) can only reference tags from the Container Subscriptions Tags catalog (i.e. /subscriptions/containers/tags). Kubex provides an initial, default set of system attributes for each <platformType> catalog. You can extend these default sets by adding additional system attributes, or you can customize the sets by modifying or deleting existing attributes. Only Kubex standard attributes or technology-specific attributes (e.g. AWS, Containers) can be added to the platform-specific Subscriptions Tags catalogs. Contact support@kubex.ai for a complete list of available Kubex standard attributes. See Default Cloud Attribute Tags or Default Container Attribute Tags.
Attributes in the platform-specific Subscriptions Tags catalog can be declared as global or private (i.e. user-specific). Global attribute tags can be used by any API enabled user, whereas private attributes can only be used by their owners. Note that have access to both global and private attributes for all users.
Resource
If you use this resource without the
<platformType> specified (i.e. without cloud or containers specified), the behavior is exactly the same as specifying the cloud-specific resource. This behavior enables backward compatibility with scripts using the Kubex API prior to release 12.1.6, where the platform-specific indicator was not available.