gcloud alpha compute global-vm-extension-policies create

NAME
gcloud alpha compute global-vm-extension-policies create - create a Compute Engine global VM extension policy
SYNOPSIS
gcloud alpha compute global-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] [--rollout-conflict-behavior=ROLLOUT_CONFLICT_BEHAVIOR] [--rollout-custom-plan=ROLLOUT_CUSTOM_PLAN] [--rollout-predefined-plan=ROLLOUT_PREDEFINED_PLAN] [--version=KEY=VALUE,[KEY=VALUE,…]] [GCLOUD_WIDE_FLAG …]
DESCRIPTION
(ALPHA) Create a Compute Engine global VM extension policy.
EXAMPLES
To create a global VM extension policy, run: 
gcloud alpha compute global-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 --rollout-predefined-plan=slow_rollout --priority=1000
POSITIONAL ARGUMENTS
NAME
Name of the global 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 project/folder 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.

--rollout-conflict-behavior=ROLLOUT_CONFLICT_BEHAVIOR
Specifies the behavior of a rollout if a conflict is detected between a zonal policy and a global policy. See gcloud compute zone-vm-extension-policies for more details on zonal policies.

The possible values are:

  • "": The zonal policy value is used in case of a conflict. This is the default behavior.
  • overwrite: The global policy overwrites the zonal policy.

If you set --rollout-conflict-behavior to overwrite and want to revert to the default behavior, use the update command and omit the --rollout-conflict-behavior flag.

--rollout-custom-plan=ROLLOUT_CUSTOM_PLAN
Provide the name of a custom rollout plan to be used for the rollout.

One of either --rollout-predefined-plan or --rollout-custom-plan must be specified, but not both.

--rollout-predefined-plan=ROLLOUT_PREDEFINED_PLAN
Provide the name of a predefined rollout plan from [fast_rollout, slow_rollout] to be used for the rollout.

One of either --rollout-predefined-plan or --rollout-custom-plan must be specified, but not both.

ROLLOUT_PREDEFINED_PLAN must be one of: fast_rollout, slow_rollout.

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

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. This variant is also available: 
gcloud beta compute global-vm-extension-policies create