NAME
    gcloud compute zone-vm-extension-policies create - create a Compute Engine
        zone VM extension policy

SYNOPSIS
    gcloud compute zone-vm-extension-policies create NAME
        --extensions=EXTENSION_NAME,[...] [--config=KEY=VALUE,[KEY=VALUE,...]]
        [--config-from-file=KEY=FILE_PATH,[...]] [--description=DESCRIPTION]
        [--inclusion-labels=INCLUSION_LABELS]
        [--priority=PRIORITY; default=1000]
        [--version=KEY=VALUE,[KEY=VALUE,...]] [--zone=ZONE]
        [GCLOUD_WIDE_FLAG ...]

DESCRIPTION
    Create a Compute Engine zone VM extension policy.

EXAMPLES
    To create a zone VM extension policy, run:

        $ gcloud compute zone-vm-extension-policies create \
            test-policy-name --description="test policy" \
            --extensions=extension1,extension2 \
            --version=extension1=version1,extension2=version2 \
            --config=extension1="config1",extension2="config2" \
            --inclusion-labels=env=prod \
            --inclusion-labels=env=preprod,workload=load-test \
            --priority=1000

        Available extensions:
          ops-agent
          google-cloud-sap-extension
          google-cloud-workload-extension

POSITIONAL ARGUMENTS
     NAME
        Name of the zone vm extension policy to create.

REQUIRED FLAGS
     --extensions=EXTENSION_NAME,[...]
        One or more extensions to be added to the policy.

OPTIONAL FLAGS
     --config=KEY=VALUE,[KEY=VALUE,...]
        A comma separated key:value list where the key is the extension name
        and the value is the desired config for the given extension. The
        extension name must be one of the extensions specified in the
        --extensions flag.

        E.g. --config=filestore='filestore config',ops-agent='ops agent config'

        Raises: ArgumentTypeError: If the extension name is not specified in
        the --extensions flag.

     --config-from-file=KEY=FILE_PATH,[...]
        Same as --config except that the value for the entry will be read from
        a local file. The extension name must be one of the extensions
        specified in the --extensions flag.

        It is an error to specify the same extension in both --config and
        --config-from-file.

     --description=DESCRIPTION
        An optional text description for the extension policy.

     --inclusion-labels=INCLUSION_LABELS
        A list of inclusion labels to select the target VMs.

        The expected format for a single selector is "key1=value1,key2=value2".
        A VM is selected if it has ALL the inclusion labels.

        When the option is specified multiple times, it assumes a logical OR
        between the selectors.

        For example, if the inclusion labels are ["env=prod,workload=frontend",
        "workload=backend"], the following VMs will be selected:
        ◆ VM1: env=prod, workload=frontend, something=else
        ◆ VM2: env=prod, workload=backend But not:
        ◆ VM3: env=prod

        If not specified, ALL VMs in the zone will be selected.

     --priority=PRIORITY; default=1000
        The priority of the policy. Lower the number, higher the priority. When
        two policies try to apply the same extension to a VM, the policy with
        higher priority takes precedence. If the priorities are the same, the
        policy with the more recent update timestamp takes precedence. If a
        policy is deleted, the extension remains installed on the VM if a
        lower-priority policy still applies.

        Range from 0 to 65535. Default is 1000.

     --version=KEY=VALUE,[KEY=VALUE,...]
        A comma separated key:value list where the key is the extension name
        and the value is the desired version for the given extension. The
        extension name must be one of the extensions specified in the
        --extensions flag. If no version is specified for an extension, the
        latest version will be used and will be upgraded automatically.

        E.g. --version=filestore=123ABC,ops-agent=456DEF

        Raises: ArgumentTypeError: If the extension name is not specified in
        the --extensions flag.

     --zone=ZONE
        Zone of the zone vm extension policy to create. If not specified and
        the compute/zone property isn't set, you might be prompted to select a
        zone (interactive mode only).

        To avoid prompting when this flag is omitted, you 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
    These variants are also available:

        $ gcloud alpha compute zone-vm-extension-policies create

        $ gcloud beta compute zone-vm-extension-policies create

