Cloud Services

ModernOps configuration

Tag definition scenarios
Published On May 16, 2024 - 1:59 PM

Tag definition scenarios

Discover example scenarios that illustrate how you might use the tag schema feature in your environment.

Scenario A: Setting a value to be determined by another value

In this scenario, you want your customer to have to choose whether the organization is shared or not when they create a production environment; and to do so, complete the following steps:
  1. Create a tag definition called
    org-environment
     that has the
    Value Type
     of
    Enum
     with the
    Tag Value Constraint
     of
    development,production
    .
  2. Create a tag definition called
    org-shared
     that has the
    Value Type
     of
    Enum
     with the
    Tag Value Constraint
     of
    True,False
    .
    You could also have the value automatically determined by setting only one value.
  3. In the
    Tag/Value Relationships
     section for
    org-shared
    , enter the following information:
    • Define a Related Tag Definition:
       Select
      org-environment
      .
    • Related Value:
       Select
      production
      .

Scenario B: Setting a value to be queried only if a value is selected

In this scenario, you want your customer to be able to select any value for the application if that customer creates a production environment; and to do so, complete the following steps:
  1. Create a tag definition called
    org-environment
     that has the
    Value Type
     of
    Enum
     with the
    Tag Value Constraint
     of
    development,production
    .
  2. Create a tag definition called
    org-application
     that has the
    Value Type
     of
    String
    .
  3. In the
    Tag/Value Relationships
     section for
    org-application
    , enter the following information:
    • Define a Related Tag Definition:
       Select
      org-environment
      .
    • Related Value:
       Select
      production
      .
In this setup, the
org-application
 tag will not be enabled unless the user assigns the value
production
 to the
org-environment
 tag.

Scenario C: Creating a hierarchy of tags

You can create a nested series of tag definitions so that one value determines a definition which in turn determines another definition. In this example, you require that in a taggable resource for which the
org-environment
 tag key is set to the
production
 value, the user is allowed to select an appropriate value for the
org-department
 tag key from an enumeration of applicable values.
In addition, you require that if the value of the
org-department
 tag key is assigned the value
b2b-analytics
, the
org-compliance
 tag key is assigned the
confidential
 value. In this hierarchy of tags, if the user does not assign the value
production
 to the
org-environment
 tag, the remaining relationships will not be enabled. If you want to create this configuration, complete the following steps:
  1. Create a tag definition called
    org-environment
     that has the
    Value Type
     of
    Enum
     with the
    Tag Value Constraint
     of
    development,production
    .
  2. Create a tag definition called
    org-department
     that has the
    Value Type
     of
    Enum
     with the
    Tag Value Constraint
     that includes
    b2-analytics
    .
  3. In the
    Tag/Value Relationships
     section for
    org-department
    , enter the following information:
    • Define a Related Tag Definition:
       Select
      org-environment
      .
    • Related Value:
       Select
      production
      .
  4. Create a tag definition called
    org-compliance
     that has the
    Value Type
     of
    Enum
     with the
    Tag Value Constraint
     of
    confidential
    .
  5. In the
    Tag/Value Relationships
     section for
    org-compliance
    , enter the following information:
    • Define a Related Tag Definition:
       Select
      org-department
      .
    • Related Value:
       Select
      b2-analytics
      .
Do you have two minutes for a quick survey?
Take Survey