The sub-commands of doctl compute tag manage the tags on your account.
Tags are labels that you can apply to resources to better organize them and more efficiently take actions on them. For example, if you have a group of Droplets that you want to place behind the same set of cloud firewall rules, you can tag those Droplets with a common tag and then apply the firewall rules to all Droplets with that tag.
You can tag Droplets, images, volumes, volume snapshots, and database clusters.
Tags have two attributes: a user defined name attribute and an embedded resources attribute with information about resources that have been tagged.
| Option | Description |
|---|---|
--help
, -h
|
Help for this command |
| Command | Description |
|---|---|
| doctl compute | Display commands that manage infrastructure |
| doctl compute tag apply | Apply a tag to resources |
| doctl compute tag create | Create a tag |
| doctl compute tag delete | Delete a tag |
| doctl compute tag get | Retrieve information about a tag |
| doctl compute tag list | List all tags |
| doctl compute tag remove | Remove a tag from resources |
| Option | Description |
|---|---|
--access-token, -t
|
API V2 access token |
--api-url, -u
|
Override default API endpoint |
--config, -c
|
Specify a custom config file
Default:
|
--context
|
Specify a custom authentication context name |
--http-retry-max
|
Set maximum number of retries for requests that fail with a 429 or 500-level error
Default: 5
|
--http-retry-wait-max
|
Set the minimum number of seconds to wait before retrying a failed request
Default: 30
|
--http-retry-wait-min
|
Set the maximum number of seconds to wait before retrying a failed request
Default: 1
|
--interactive
|
Enable interactive behavior. Defaults to true if the terminal supports it (default false)
Default: false
|
--output, -o
|
Desired output format [text|json]
Default: text
|
--trace
|
Show a log of network activity while performing a command
Default: false
|
--verbose, -v
|
Enable verbose output
Default: false
|