gcloud alpha compute instances update-from-file

NAME: gcloud alpha compute instances update-from-file - update a Compute Engine virtual machine instance using a configuration file
SYNOPSIS: gcloud alpha compute instances update-from-file INSTANCE_NAME [--clear-secure-tag] [--minimal-action=MINIMAL_ACTION] [--most-disruptive-allowed-action=MOST_DISRUPTIVE_ALLOWED_ACTION] [--source=SOURCE] [--zone=ZONE] [GCLOUD_WIDE_FLAG …]
DESCRIPTION: (ALPHA) Update a Compute Engine virtual machine instance using a configuration file. For more information, see https://cloud.google.com/compute/docs/instances/update-instance-properties.
EXAMPLES: A virtual machine instance can be updated by running:
gcloud alpha compute instances update-from-file my-instance --source=<path-to-file>
POSITIONAL ARGUMENTS: INSTANCE_NAME

Name of the instance to update. 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: --clear-secure-tag

If specified, all secure tags bound to this instance will be removed.

--minimal-action=MINIMAL_ACTION

If specified, this action or higher level action is performed on the instance irrespective of what action is required for the update to take effect. If not specified, then Compute Engine acts based on the minimum action required.

--most-disruptive-allowed-action=MOST_DISRUPTIVE_ALLOWED_ACTION

If specified, Compute Engine returns an error if the update requires a higher action to be applied to the instance. If not specified, the default will be REFRESH.

--source=SOURCE

Path to a YAML file containing configuration export data. Alternatively, you may omit this flag to read from standard input.For a schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/alpha/Instance.yaml.
Note: $CLOUDSDKROOT represents the Google Cloud CLI's installation directory.

--zone=ZONE

Zone of the instance to update. If not specified, you might be prompted to select a zone (interactive mode only). gcloud attempts to identify the appropriate zone by searching for resources in your currently active project. If the zone cannot be determined, gcloud prompts 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/zone property:
gcloud config set compute/zone ZONE

A list of zones can be fetched by running:
gcloud compute zones list

To unset the property, run:
gcloud config unset compute/zone

Alternatively, 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 help for details.
NOTES: This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early access allowlist. These variants are also available:
gcloud compute instances update-from-file

gcloud beta compute instances update-from-file