The following command sets an object's custom-metadata:
gdcloud storage objects update s3://my-bucket/my-object --custom-metadata=key1=value1,key2=value2
The following command updates an object's custom-metadata:
gdcloud storage objects update s3://my-bucket/my-object --update-custom-metadata=key1=value1,key2=value2
OPTIONAL FLAGS
--cache-control string How caches should handle requests and responses.
--clear-custom-metadata Clear all custom metadata on objects. When used with --preserve-posix,
POSIX attributes are still stored in custom metadata.
--content-disposition string How content should be displayed.
--content-encoding string How content is encoded (e.g. gzip).
--content-language string Content's language (e.g. "en" signifies "English").
--content-md5 string Manually specified MD5 hash digest for the contents of an uploaded
file. This flag cannot be used when uploading multiple files.
--content-type string Type of data contained in the object (e.g. text/html).
-c, --continue-on-error If any operations are unsuccessful, the command will exit with a non-zero
exit status after completing the remaining operations. This flag takes
effect only in sequential execution mode (i.e. processor and thread count
are set to 1). Parallelism is default.
--custom-metadata stringToString Set custom metadata on objects. When used with --preserve-posix, POSIX
attributes are also stored in custom metadata. (default [])
--log-http Log all HTTP server requests and responses to stderr.
-r, --recursive Recursively copy the contents of any directories that match the source
path expression.
--remove-custom-metadata stringArray Remove individual custom metadata keys from objects. This flag can be
used with --update-custom-metadata. When used with --preserve-posix,
POSIX attributes specified by this flag are not preserved.
--update-custom-metadata stringToString Add or set individual custom metadata key-value pairs on objects.
Existing custom metadata not specified with this flag is not changed. This
flag can be used with --remove-custom-metadata. When keys overlap with
those provided by --preserve-posix, values specified by this flag are used. (default [])
--verbosity string Override the default verbosity for this command. VERBOSITY must be one of:
debug, info, warning, error, critical, none. (default "warning")
GDCLOUD WIDE FLAGS
These flags are available to all commands: --configuration, --format, --help, --project, --quiet.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-25 UTC."],[[["\u003cp\u003eThis command, \u003ccode\u003egdcloud storage objects update\u003c/code\u003e, allows users to modify object storage objects.\u003c/p\u003e\n"],["\u003cp\u003eUsers can update various attributes of storage objects, including \u003ccode\u003ecache-control\u003c/code\u003e, \u003ccode\u003econtent-disposition\u003c/code\u003e, \u003ccode\u003econtent-encoding\u003c/code\u003e, \u003ccode\u003econtent-language\u003c/code\u003e, \u003ccode\u003econtent-md5\u003c/code\u003e, and \u003ccode\u003econtent-type\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eThe command supports managing custom metadata through options like \u003ccode\u003e--custom-metadata\u003c/code\u003e, \u003ccode\u003e--clear-custom-metadata\u003c/code\u003e, \u003ccode\u003e--remove-custom-metadata\u003c/code\u003e, and \u003ccode\u003e--update-custom-metadata\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003e--recursive\u003c/code\u003e flag enables the command to recursively update objects within directories, and the \u003ccode\u003e--continue-on-error\u003c/code\u003e option allows the command to proceed despite errors.\u003c/p\u003e\n"],["\u003cp\u003eHTTP request and response logging is available with the \u003ccode\u003e--log-http\u003c/code\u003e flag, and verbosity of the output can be controlled via the \u003ccode\u003e--verbosity\u003c/code\u003e flag.\u003c/p\u003e\n"]]],[],null,["# gdcloud storage objects update\n\nNAME\n----\n\ngdcloud storage objects update - Update object storage objects.\n\nSYNOPSIS\n--------\n\n gdcloud storage objects update [URL ...]\n [--continue-on-error, -c]\n [--recursive, -r]\n [--cache-control=CACHE_CONTROL]\n [--content-disposition=CONTENT_DISPOSITION]\n [--content-encoding=CONTENT_ENCODING]\n [--content-language=CONTENT_LANGUAGE]\n [--content-md5=MD5_DIGEST]\n [--content-type=CONTENT_TYPE]\n [--custom-metadata=[CUSTOM_METADATA,...]]\n [--clear-custom-metadata]\n [--remove-custom-metadata=[CUSTOM_METADATA,...]]\n [--update-custom-metadata=[CUSTOM_METADATA,...]]\n [--format=FORMAT]\n [--log-http]\n [--verbosity=VERBOSITY] [flags]\n\n### EXAMPLES\n\n The following command sets an object's custom-metadata:\n\n gdcloud storage objects update s3://my-bucket/my-object --custom-metadata=key1=value1,key2=value2\n\n The following command updates an object's custom-metadata:\n\n gdcloud storage objects update s3://my-bucket/my-object --update-custom-metadata=key1=value1,key2=value2\n\n### OPTIONAL FLAGS\n\n --cache-control string How caches should handle requests and responses.\n --clear-custom-metadata Clear all custom metadata on objects. When used with --preserve-posix,\n POSIX attributes are still stored in custom metadata.\n --content-disposition string How content should be displayed.\n --content-encoding string How content is encoded (e.g. gzip).\n --content-language string Content's language (e.g. \"en\" signifies \"English\").\n --content-md5 string Manually specified MD5 hash digest for the contents of an uploaded\n file. This flag cannot be used when uploading multiple files.\n --content-type string Type of data contained in the object (e.g. text/html).\n -c, --continue-on-error If any operations are unsuccessful, the command will exit with a non-zero\n exit status after completing the remaining operations. This flag takes\n effect only in sequential execution mode (i.e. processor and thread count\n are set to 1). Parallelism is default.\n --custom-metadata stringToString Set custom metadata on objects. When used with --preserve-posix, POSIX\n attributes are also stored in custom metadata. (default [])\n --log-http Log all HTTP server requests and responses to stderr.\n -r, --recursive Recursively copy the contents of any directories that match the source\n path expression.\n --remove-custom-metadata stringArray Remove individual custom metadata keys from objects. This flag can be\n used with --update-custom-metadata. When used with --preserve-posix,\n POSIX attributes specified by this flag are not preserved.\n --update-custom-metadata stringToString Add or set individual custom metadata key-value pairs on objects.\n Existing custom metadata not specified with this flag is not changed. This\n flag can be used with --remove-custom-metadata. When keys overlap with\n those provided by --preserve-posix, values specified by this flag are used. (default [])\n --verbosity string Override the default verbosity for this command. VERBOSITY must be one of:\n debug, info, warning, error, critical, none. (default \"warning\")\n\n### GDCLOUD WIDE FLAGS\n\nThese flags are available to all commands: `--configuration`, `--format`, `--help`, `--project`, `--quiet`.\n\nFor more information, see the [gdcloud CLI reference overview](/distributed-cloud/hosted/docs/latest/gdch/resources/gdcloud-reference/gdcloud) page."]]