CloudBolt supports managing AWS and VMware (v6.5+) tags on your servers by linking them to CloudBolt server attributes. When the value of the CloudBolt attribute changes on the server, so will the value of the tag.
How to Use Tags¶
An example use-case is to manage AWS cost center tags. Say you want servers provisioned by your Dev group to have the Cost Center tag set to 1. Here are the steps to make that happen:
- Create a new Cost Center parameter in the Admin interface. Make sure to select “Show on servers” to make the parameter taggable, and select “Required” if you want to hide it on the order form.
- Add the parameter to the Dev group, and add 1 as the sole option.
- Under the Tags tab of the resource handler, add a new tag, Enter Cost Center as the Tag Name, and select cost_center as the attribute.
Now whenever the Dev group provisions a server, the Cost Center parameter and tag will both be set to 1.
Tags are created on the server at provision time, but they can also be updated on servers at any time. If you edit a parameter on a server in CloudBolt, it will automatically write the new value to the linked tag.
Likewise, changes to tags in the Resource Handler can be detected by CloudBolt. When you run the Refresh Info server action on a server, CloudBolt will not only update the “Tags” section of the server, but also the “Parameters” section for any parameters that are linked to tags.
Syncing from remote tags is only supported for Parameters, not built-in server attributes like owner, environment, or group.
For VMware, CloudBolt will treat all tags as if they have single cardinality, meaning there can be only one tag value per category per VM. If you make a category in VMware that supports multiple tags, only one of those tag’s values will show on the server in CB. Also, it’s important to be aware that if you were to change the value of the parameter associated with that tag in CB, all the other values would be removed from that VM.