You can add tags to your product portfolios, products, and instances in Service Catalog. This allows you to categorize resources, allocate costs, and perform automatic O&M based on the tags.
Overview
Administrators can define various TagOptions in the TagOptions library and associate the TagOptions with product portfolios and products. When an end user launches a product or updates a product instance in Service Catalog, Service Catalog automatically associates the product or the instance with tags that correspond to the TagOptions preset by the administrator. The end user can also define custom TagOptions to associate the product or the instance with other custom tags. This way, end users can add the required tags to resources when the end users create instances, and thus will not forget to add tags or use noncompliant tags.
Rules of aggregating TagOptions
Administrators can associate TagOptions with product portfolios and products. A product portfolio or product can be associated with multiple TagOptions. Service Catalog aggregates the TagOptions that are associated with a product portfolio or product and determines the valid TagOptions based on scenario-specific rules. When an end user launches a product or updates an instance, the end user can view the valid aggregated TagOptions.
Scenario | TagOption associated with the product | TagOption associated with the product portfolio | Valid TagOption during the product launch or the instance update | Aggregation rule |
A product is associated with TagOptions but the product portfolio to which the product belongs is not associated with the TagOptions. |
| None |
| If the keys of TagOptions that are associated with the product portfolio and the product do not overlap, all associated TagOptions are valid. |
| None |
|
| |
A product portfolio is associated with TagOptions but the product that belongs to the portfolio is not associated with TagOptions. | None |
|
| If the keys of the TagOptions that are associated with the product portfolio and the product do not overlap, all associated TagOptions are valid. |
None |
|
|
| |
A product portfolio and the product in the portfolio are associated with TagOptions. |
|
|
| If the keys of TagOptions that are associated with the product portfolio and the product do not overlap, all associated TagOptions are valid. |
|
|
| If the keys of the TagOptions that are associated with the product portfolio and the product overlap and the overlapped key has the same value, the overlapped key-value pair is deduplicated and other key-value pairs are retained in valid TagOptions. | |
|
|
| If the keys of the TagOptions that are associated with the product portfolio and the product overlap and the overlapped key has the same value, only the overlapped key-value pair is deduplicated and retained in valid TagOptions. | |
|
| TagOptions conflict. | If the keys of TagOptions that are associated with the product portfolio and the product overlap and the overlapped key has different values, a message that indicates the TagOptions conflict is returned. In this case, the end user cannot launch the product or update the instance. |
Limits
Item | Limits |
TagOption key | A TagOption key must be 1 to 128 characters in length and cannot contain |
TagOption value | A TagOption value must be 1 to 128 characters in length and cannot contain |
Maximum number of TagOptions that can be created within an Alibaba Cloud account | 1,000 |
Maximum number of TagOptions that can be associated with a product portfolio | 25 |
Maximum number of TagOptions that can be associated with a product | 25 |
Maximum number of TagOption values for a TagOption key | 25 |