Boundary
storage-buckets update
Enterprise
This feature requires HCP Boundary or Boundary Enterprise
Command: boundary storage-buckets update
The boundary storage-buckets update command lets you update Boundary storage buckets by ID.
Example
This example updates a storage bucket with the ID _1234567890 to add the name devops and the description storage bucket for DevOps:
$ boundary storage-buckets update -id _1234567890 -name devops -description "storage bucket for DevOps"
Usage
$ boundary storage-buckets update [options] [args]
Command options
-description=<string>- The description to set for the storage bucket.-id=<string>- The ID of the storage bucket you want to update.-name=<string>- The name to set for the storage bucket.-version=<int>- The version of the storage bucket against which to perform the update operation. If you do not specify a version, the command performs a check-and-set operation automatically.
Attribute options
-attr- A key=value pair to add to the request's attribute map. This option can also be a key value only, which sets a JSON null as the value. If you provide a value, Boundary automatically infers the type. You can override the type using-string-attr,-bool-attr, or-num-attr. You can specify this value multiple times. This option supports referencing values from files usingfile://and environment variables usingenv://.-attributes=<string>- A JSON map value that you can use as the entirety of the request's attributes map. Usually this value is sourced from a file using thefile://syntax. This option is exclusive with otherattrflags.-bool-attr- A key=value Boolean value that you can add to the request's attributes map. You can specify this value multiple times. This option supports referencing values from files usingfile://and environment variables usingenv://.-num-attr- A key=value numeric value that you can add to the request's attributes map. You can specify this value multiple times. This attribute supports referencing values from files usingfile://and environment variables usingenv://.-string-attr- A key=value string value that you can add to the request's attributes map. You can specify this value multiple times. This option supports referencing values from files usingfile://and environment variables usingenv://.
Secrets options
-bool-secret- A key=value Boolean value that you can add to the request's secrets map. You can specify this value multiple times. This option supports referencing values from files usingfile://and environment variables usingenv://.-num-secret- A key=value numeric value that you can add to the request's secrets map. You can specify this value multiple times. This option supports referencing values from files usingfile://and environment variables usingenv://.-secret- A key=value pair that you can add to the request's secrets map. This option can also be a key value only, which sets a JSON null as the value. If you provide a value, Boundary automatically infers the type. You can override the type using-string-secret,-bool-secret, or-num-secret. You can specify this value multiple times. This option supports referencing values from files usingfile://and environment variables usingenv://.-secrets=<string>- A JSON map value that you can use as the entirety of the request's secrets map. Usually this value is sourced from file usingfile://syntax. This option is exclusive with other secret flags.-string-secret- A key=value string value that you can add to the request's attributes map. You can specify this value multiple times. This option supports referencing values from files usingfile://and environment variables usingenv://.
Storage bucket options
-worker-filter=<string>- A Boolean expression that you can use to filter which workers can process communication to the storage bucket.