Services

Explore Kyndryl Bridge Services

Tag repository
Published On Jun 11, 2026 - 10:07 AM

Tag repository

Understand the Tag repository as a single source for accessing a categorized set of tags, minimizing duplicate tags and administrator confusion.
The tag repository enables users to add or manage tags through four main capabilities:
  1. Add tag values from active tags created on the Tag Definition page.
  2. Create a new key or value pair directly within the repository.
  3. Import tags in bulk from external sources.
  4. Store tags pushed by other applications or services.
Tags created directly from the tag repository are labeled non-compliant because they lack definitions. However, the administrator can still use these tags and update their definitions later on from the Tag Definitions page.

Viewing the tag repository

All tags added to the repository are uniformly applicable at an account level, making the system straightforward to understand. The tag repository only has active tag keys.
The tag repository page displays all the tags for the applications or services used. Under the
used by
 column, you can view all associated tags with one or more applications.
To identify governed tags, a column has been added to indicate whether a tag has a definition (tags formally defined with the necessary details to specify how they should be used, values they can take, or overall purpose). Non-compliant tag values with the defined constraints are also displayed in the
Tag Definition
 page. Click the
View Details
 option of a specific tag to view the latest tag editor, creator, and creation date.

Capability 1: Add tag values from active tags created on the Tag Definition page

The system is designed to prevent errors. If you, as the tag administrator, add tag values that are outside the constraints established on the tag definitions page, the system will display an error message and stop the addition of such values, ensuring the integrity of the tag repository.
To add a tag value
  1. Go to the
    Tag Repository
    . Go to the page and look for the tag key that requires an update.
  2. Click the
    View Details
     option and select
    Add tag values
    .
  3. Add all the required values, separated by commas. The set constraints are displayed to ensure that the values added are compliant. An error message will be displayed for non-compliant values.
  4. Once all values are added, click the
    Add Tag(s)
     button. The window closes, and a new message displays on the page: “Tag value(s) successfully added. You have successfully added values [name], [name] to key [name]”.
To delete a tag value
  1. Select the tag that requires the update.
  2. Click the expandable icon to review the definition of compliance for each value.
  3. Select the value that needs to be deleted and click the options icon.
  4. Select the
    Delete
    option. A new window pops up requesting to confirm this action.
  5. Click the
    Delete Value
     button to confirm the deletion. Otherwise, click
    Cancel
    .
Once deleted, the window closes, and a message displays: “Tag value [name] deleted successfully. You have successfully deleted tag value [name] from the tag [name]”.

Capability 2: Create a new key or value pair directly within the repository

An administrative control capability at an account level allows the enabling or disabling of the creation of tags directly to the tag repository. For additional details, see administrative control.
If you create a new tag using a tag key already in the repository but without a tag value, the system will suggest similar tag keys already available, ensuring consistency and avoiding duplication.
To add a tag
  1. Go to the
    Tag Repository
     page and click the
    Add Tags
     button. A new window opens.
  2. Select whether you will add new tag(s) or bulk add tags.
  3. Enter a unique tag key. The tag management allows tag keys with a minimum of 1 character and a maximum of 256 characters, including numbers from 0 to 9 and special characters (!@$%*();: _ - / \ ).
  4. Enter all the tag values associated with the key, separated by commas.
  5. Once you have completed all the information, click the
    Add Tags
     button at the bottom of the window.
Delete tags
Account administrators can delete tags with no associated resources/applications. You will have the option to delete all unused tags or delete an unused tag.
To delete an unused tag:
  1. Go to the
    Tag Repository
    . On the page, look for the tag key that needs to be eliminated.
  2. Click the
    view details
     option and select
    Delete
     .
To delete all unused tags:
  1. From the
    Tag Repository
     table, select all the tags that need to be removed and click the
    Delete Tags
     button at the top.

Capability 3: Import tags to the Tag Repository page

This functionality enables the efficient simultaneous importation of many tags into the repository to create multiple tags. Account administrators can define account-specific tags in bulk and upload a JSON/CSV template to create multiple tags.
Perform the following procedure to import tags in bulk:
  1. From the
    Tag Repository
     page, select the
    Add Tags
     button. A window opens.
  2. Select the
    Bulk add tags
    option.
  3. Drag, drop, or choose the JSON or CSV file containing the tags you want to import. The file should not exceed 1 MB in size. The template should have two mandatory fields: tag key and tag value. Otherwise, an alert message displays: '
    This file is missing the required columns.
    or
    This file exceeds the 1 MB file size limit.
    ' . A sample file is available for reference; download and review this sample before uploading your import file.
  4. If you no longer want to import the file you selected, click the
    remove
     link to discard it. If you no longer want to continue with this operation, click
    Cancel
     to exit this window.
  5. When the system validates the file, click the
    Upload
     button to proceed with the import. A notification indicates whether the process has been completed successfully or partially.
The system imports tags that are unavailable in the tag repository. To ensure data integrity, the system imports only the value once for duplicate entries. You can maintain the same file and continue adding tags as needed. When uploading the same file with the latest updates, only the new entries are imported.
When you import a tag key with the same name as an existing tag, it will automatically follow the current tag rules. For example, if you import a tag key called 'Team' and 'Team' already exists in the tag rules, the new 'Team' tag will be compliant. Any values that do not meet the rules will be marked, indicating they require attention.
The import report in the notification details the success or failure of each entry in the import file, providing a clear understanding of the import process. It also explains the reason for failure (for example, a tag already exists, an empty field, or a duplicate value).

Capability 4: Store tags in the Tag Repository page

Tags from cloud providers and external sources, such as ServiceNow, can be sent to the tag repository through various Bridge applications and services. This integration enables applications to store tag information in the tag repository instead of within their own systems. Once applications send tag information to the repository, the repository will manage the lifecycle of those tags. The
used by
 A column in the tag repository table allows you to view all the applications that currently use a particular tag.
Discovered tags are pushed by the applications to the repository, and any updates—such as new or deleted tag values—will be reflected in the tag repository whenever a push occurs. When discovered tags are sent to the repository, any duplicate tag key/value pairs will be reconciled. If tags are pushed without an associated tag definition, the tag repository will indicate that the definition is missing for those tags.
Tags that are stored with the same key as an existing tag definition will automatically be considered compliant. For example, if a tag is pushed to the tag repository, but a tag key with the same name already has an existing tag definition, then the newly pushed tag will automatically be compliant because a definition for that tag key already exists. In such cases, tag keys will not be duplicated. However, tags discovered from external sources may not comply with the tag definitions and could be deemed non-compliant.
If an application or service adds a new value to an existing tag key in their respective application, that value will be added to the repository as well. For example, if an application or service uses the 'Environment' tag from the common tag repository and does not find a suitable value to tag with, it may create a new value called 'Production.' In this case, the new tag value should also be appended to the list of values for the 'Environment' tag in the repository. The Tag Administrator is responsible for ensuring that all values comply with the established rules.
Do you have two minutes for a quick survey?
Take Survey