- NAME
-
- gcloud beta compute instances add-partner-metadata - add or update partner metadata
- SYNOPSIS
-
-
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 …]
-
- DESCRIPTION
-
(BETA)gcloud beta compute instances add-partner-metadata can be used to add or update or patch partner metadata of a virtual machine instance. Every instance has access to a metadata server that can be used to query partner metadata that has been set through this tool. For information on metadata, see About VM metadata.Only namespaces keys that are provided are mutated. Existing Namespaces entries will remain unaffected.
In order to retrieve partner metadata, run:
gcloud compute instances describe example-instance --zoneus-central1-a --view=FULL --format="value(partnerMetadata)"where example-instance is the name of the virtual machine instance you're querying partner metadata from.
- EXAMPLES
-
To add partner metadata under namespace
test.compute.googleapis.comTEST_INSTANCEgcloud beta compute instances add-partner-metadata TEST_INSTANCE --partner-metadata=test.compute.googleapis.com/entries="{ "engine": { "type": V8 } }"To add partner metadata from a file:
gcloud beta compute instances add-partner-metadata TEST_INSTANCE --partner-metadata-from-file=examples/engine.json - POSITIONAL ARGUMENTS
-
INSTANCE_NAME- Name of the instance to set partner metadata on. For details on valid instance names, refer to the criteria documented under the field 'name' at: https://cloud.google.com/compute/docs/reference/rest/v1/instances
- FLAGS
-
--partner-metadata=[NAMESPACE/KEY=VALUE,…]- Partner metadata specifying namespace and its entries. The entries can be key-value pairs or in json format.
--partner-metadata-from-file=LOCAL_FILE_PATH- Path to a local json file containing partner metadata.
--zone=ZONE-
Zone of the instance to set partner metadata on. If not specified, you might be
prompted to select a zone (interactive mode only).
gcloudattempts to identify the appropriate zone by searching for resources in your currently active project. If the zone cannot be determined,gcloudprompts you for a selection with all available Google Cloud Platform zones.To avoid prompting when this flag is omitted, the user can set the
compute/zonegcloud config set compute/zone ZONEA list of zones can be fetched by running:
gcloud compute zones listTo unset the property, run:
gcloud config unset compute/zoneAlternatively, the zone can be stored in the environment variable
CLOUDSDK_COMPUTE_ZONE
- GCLOUD WIDE FLAGS
-
These flags are available to all commands:
--access-token-file,--account,--billing-project,--configuration,--flags-file,--flatten,--format,--help,--impersonate-service-account,--log-http,--project,--quiet,--trace-token,--user-output-enabled,--verbosity.Run
$ gcloud helpfor details. - NOTES
-
This command is currently in beta and might change without notice. This variant
is also available:
gcloud alpha compute instances add-partner-metadata
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2024-04-30 UTC.
[{
"type": "thumb-down",
"id": "hardToUnderstand",
"label":"Hard to understand"
},{
"type": "thumb-down",
"id": "incorrectInformationOrSampleCode",
"label":"Incorrect information or sample code"
},{
"type": "thumb-down",
"id": "missingTheInformationSamplesINeed",
"label":"Missing the information/samples I need"
},{
"type": "thumb-down",
"id": "otherDown",
"label":"Other"
}]
[{
"type": "thumb-up",
"id": "easyToUnderstand",
"label":"Easy to understand"
},{
"type": "thumb-up",
"id": "solvedMyProblem",
"label":"Solved my problem"
},{
"type": "thumb-up",
"id": "otherUp",
"label":"Other"
}]