gcloud compute resource-policies update instance-schedule

NAME: gcloud compute resource-policies update instance-schedule - update a Compute Engine Instance Schedule Resource Policy
SYNOPSIS: gcloud compute resource-policies update instance-schedule NAME [--description=DESCRIPTION] [--end-date=END_DATE] [--initiation-date=INITIATION_DATE] [--region=REGION] [--timezone=TIMEZONE] [--vm-start-schedule=VM_START_SCHEDULE] [--vm-stop-schedule=VM_STOP_SCHEDULE] [GCLOUD_WIDE_FLAG …]
DESCRIPTION: Update a Compute Engine Instance Schedule Resource Policy.
EXAMPLES: To update an instance schedule resource policy with specified parameters:
gcloud compute resource-policies update instance-schedule NAME --region=REGION --timezone=UTC --vm-start-schedule="0 7 * * *" --vm-stop-schedule="0 17 * * *"
POSITIONAL ARGUMENTS: NAME

Name of the resource policy to operate on.
FLAGS: --description=DESCRIPTION

An optional, textual description for the backend.

--end-date=END_DATE

The expiration time of the schedule policy. The timestamp must be an RFC3339 valid string.

--initiation-date=INITIATION_DATE

The start time of the schedule policy. The timestamp must be an RFC3339 valid string.

--region=REGION

Region of the resource policy to operate on. If not specified, you might be prompted to select a region (interactive mode only).
To avoid prompting when this flag is omitted, you can set the compute/region property:
gcloud config set compute/region REGION

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

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

Alternatively, the region can be stored in the environment variable CLOUDSDK_COMPUTE_REGION.

--timezone=TIMEZONE

Timezone used in interpreting schedule. The value of this field must be a time zone name from the tz database http://en.wikipedia.org/wiki/Tz_database

--vm-start-schedule=VM_START_SCHEDULE

Schedule for starting the instance, specified using standard CRON format.

--vm-stop-schedule=VM_STOP_SCHEDULE

Schedule for stopping the instance, specified using standard CRON format.
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: These variants are also available:
gcloud alpha compute resource-policies update instance-schedule

gcloud beta compute resource-policies update instance-schedule