Using Custom Tags

  • 11 January 2022
  • 0 replies
  • 8 views

All sandbox and production environment resources are tagged with Torque’s out-of-the-box tags. Torque uses several out-of-the-box system tags to provide you with activity and cost data. In addition, you can attach your own custom tags to your environments for your own uses, including monitoring and control, troubleshooting, and more. 

Features and limitations:

  • Custom tags apply for all blueprint types, including YAML and Terraform-based.
  • Custom tags are applied to every cloud resource that is created in the sandbox or production environment, including resources created by services (Terraform modules), and deleted from the cloud along with the environment when it is ended/renamed.
  • Custom tags are created on the account level and defined with a scope, which determines where they get their value (account, space, blueprint, and sandbox).
  • The custom tag’s value can be defined by the Torque admin, selected from a dropdown list of possible values, or entered as freetext (if possible values were not defined).
  • When a sandbox or production environment is deployed, its tags are the aggregation of the tags defined for this sandbox (in runtime), the blueprint tags, the space tags and the account tags, as well as the Torque automatic tags. 
  • Custom tags are not used in environments deployed over existing cloud infrastructure.
  • Up to 20 custom tags can be created, to avoid passing the limit of the cloud providers.

 The general process for setting up and applying custom tags is as follows:

  1. The Torque admin creates a custom tag and defines its scope (Administration > Tags).
  2. The value of the custom tag can be modified by other users, depending on its scope: 
    • For “space” custom tags: The space admin can set the custom tag’s default value for all environments deployed in the space (Settings > Tags).
    • For “blueprint” custom tags: The blueprint designer can set the custom tag’s value for all environments deployed from the blueprint (Blueprints > Advanced/Terraform Blueprints).
    • For “sandbox” custom tags: When launching a sandbox, the sandbox end-user can override the values of the sandbox’s custom tags (Sandbox Environments/Production Environments).
  3. When the sandbox is deployed, all applicable custom tags are applied (account, space, blueprint, and sandbox).
  4. When the sandbox ends, the custom tags are deleted from the cloud provider, along with the environment’s resources.

Related Articles


0 replies

Be the first to reply!

Reply