gcloud compute project-info add-metadata - add or update project-wide metadata
gcloud compute project-info add-metadata [--metadata KEY=VALUE,[KEY=VALUE,...]] [--metadata-from-file KEY=LOCAL_FILE_PATH,[KEY=LOCAL_FILE_PATH,...]] [GLOBAL-FLAG ...]
gcloud compute project-info add-metadata can be used to add or update project-wide metadata. Every instance has access to a metadata server that can be used to query metadata that has been set through this tool. Project-wide metadata entries are visible to all instances. To set metadata for individual instances, use gcloud compute instances add-metadata. For information on metadata, see https://cloud.google.com/compute/docs/metadata.
Only metadata keys that are provided are mutated. Existing metadata entries will remain unaffected.
--metadata KEY=VALUE,[KEY=VALUE,...]Metadata to be made available to the guest operating system running on the instances. Each metadata entry is a key/value pair separated by an equals sign. Metadata keys must be unique and less than 128 bytes in length. Values must be less than or equal to 32,768 bytes in length. Multiple arguments can be passed to this flag, e.g., --metadata key-1=value-1,key-2=value-2,key-3=value-3.--metadata-from-file KEY=LOCAL_FILE_PATH,[KEY=LOCAL_FILE_PATH,...]
In images that have Compute Engine tools installed (https://cloud.google.com/compute/docs/images) on them, the following metadata keys have special meanings:
startup-scriptSpecifies a script that will be executed by the instances once they start running. For convenience, --metadata-from-file can be used to pull the value from a file.startup-script-url
Same as startup-script except that the script contents are pulled from a publicly-accessible location on the web.
Same as --metadata except that the value for the entry will be read from a local file. This is useful for values that are too large such as startup-script contents.
Run $ gcloud help for a description of flags available to all commands.