gcloud alpha compute resource-policies create-vm-maintenance

NAME: gcloud alpha compute resource-policies create-vm-maintenance - create a Compute Engine VM Maintenance Resource Policy
SYNOPSIS: gcloud alpha compute resource-policies create-vm-maintenance NAME (--daily-window --start-time=START_TIME) [--description=DESCRIPTION] [--region=REGION] [GCLOUD_WIDE_FLAG …]
DESCRIPTION: (ALPHA) (DEPRECATED) create-vm-maintenance is deprecated. Use compute resource-policies create vm-maintenance instead. Create a Compute Engine VM Maintenance Resource Policy.
EXAMPLES: The following command creates a Compute Engine VM Maintenance Resource Policy with a daily maintenance activity window that starts at 04:00Z.
gcloud alpha compute resource-policies create-vm-maintenance my-resource-policy --region=REGION --start-time=04:00Z --daily-window
POSITIONAL ARGUMENTS: NAME

Name of the resource policy to operate on.
REQUIRED FLAGS: Cycle Frequency Group.
This must be specified.

--daily-window

Maintenance activity window starts daily at START_TIME.
This flag argument must be specified if any of the other arguments in this group are specified.

--start-time=START_TIME

Start time of a four-hour window in which maintenance should start in daily cadence. Valid choices are 00:00, 04:00, 08:00, 12:00, 16:00 and 20:00 UTC. For example, --start-time="08:00".
This flag argument must be specified if any of the other arguments in this group are specified.
OPTIONAL FLAGS: --description=DESCRIPTION

An optional, textual description for the backend.

--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.
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.