gcloud beta compute instances add-partner-metadata - add or update partner metadata

gcloud beta compute instances add-partner-metadataINSTANCE_NAME[--partner-metadata=[NAMESPACE/KEY=VALUE,…]][--partner-metadata-from-file=LOCAL_FILE_PATH][--zone=ZONE][GCLOUD_WIDE_FLAG …]

Only namespaces keys that are provided are mutated. Existing Namespaces entrieswill remain unaffected.

In order to retrieve partner metadata, run:

gcloudcomputeinstancesdescribeexample-instance--zoneus-central1-a--view=FULL--format="value(partnerMetadata)"

where example-instance is the name of the virtual machine instance you'requerying partner metadata from.

gcloudbetacomputeinstancesadd-partner-metadataTEST_INSTANCE--partner-metadata=test.compute.googleapis.com/entries="{ "engine": { "type": V8 } }"

To add partner metadata from a file:

gcloudbetacomputeinstancesadd-partner-metadataTEST_INSTANCE--partner-metadata-from-file=examples/engine.json

INSTANCE_NAME

Name of the instance to set partner metadata on. For details on valid instancenames, refer to the criteria documented under the field 'name' at:https://cloud.google.com/compute/docs/reference/rest/v1/instances

--partner-metadata=[NAMESPACE/KEY=VALUE,…]

Partner metadata specifying namespace and its entries. The entries can bekey-value pairs or in json format.

--partner-metadata-from-file=LOCAL_FILE_PATH

Path to a local json file containing partner metadata. Use a full or relativepath to a local file containing the value of partner_metadata.

--zone=ZONE

Zone of the instance to set partner metadata on. If not specified, you might beprompted to select a zone (interactive mode only).gcloud attempts to identify theappropriate zone by searching for resources in your currently active project. Ifthe zone cannot be determined,gcloud prompts you for a selection withall available Google Cloud Platform zones.

To avoid prompting when this flag is omitted, the user can set thecompute/zone property:

gcloudconfigsetcompute/zoneZONE

A list of zones can be fetched by running:

gcloudcomputezoneslist

To unset the property, run:

gcloudconfigunsetcompute/zone

Alternatively, the zone can be stored in the environment variableCLOUDSDK_COMPUTE_ZONE.

Run$gcloud help for details.