gcloud alpha assured v2 workloads create

NAME

gcloud alpha assured v2 workloads create - create a new Assured Workloads V2 environment

SYNOPSIS

gcloud alpha assured v2 workloads create [[WORKLOAD_ID] --external-identifier=EXTERNAL_IDENTIFIER     | --workload-id=FLAG_WORKLOAD_ID] --framework=FRAMEWORK --location=LOCATION --organization=ORGANIZATION (--new-folder-config=[PROPERTY=VALUE,…]     | --new-project-config=[PROPERTY=VALUE,…]     | --target-folder=TARGET_FOLDER     | --target-project=TARGET_PROJECT) [--async] [--cmek-dedicated-project-config=[PROPERTY=VALUE,…]] [--cmek-key-ring=CMEK_KEY_RING] [--description=DESCRIPTION] [--framework-major-revision=FRAMEWORK_MAJOR_REVISION] [--cloud-control-config=[PROPERTY=VALUE,…]     | --cloud-control-configs-from-file=CLOUD_CONTROL_CONFIGS_FROM_FILE] [GCLOUD_WIDE_FLAG …]

DESCRIPTION

(ALPHA) Create a new Assured Workloads V2 environment.

EXAMPLES

To create an Assured Workload onboarding an existing project:

gcloud alpha assured v2 workloads create my-workload --organization=123 --location=us-central1 --description="My Workload" --target-project=projects/456 --framework=fedramp-moderate

To create an Assured Workload provisioning a new project with CMEK:

gcloud alpha assured v2 workloads create --organization=123 --location=us-central1 --description="CMEK Workload" --new-project-config=project_id=custom-id,billing_account=billingAccounts/456 --framework=il4 --cmek-key-ring=projects/kms-p/locations/us-central1/keyRings/r1

POSITIONAL ARGUMENTS

At most one of these can be specified:

[WORKLOAD_ID]

User-assigned unique identifier for the workload. If omitted, generated by the server.

--external-identifier=EXTERNAL_IDENTIFIER

Backwards-compatible alias for --workload-id.

--workload-id=FLAG_WORKLOAD_ID

User-assigned unique identifier for the workload.

REQUIRED FLAGS

--framework=FRAMEWORK

Compliance framework resource name or ID (e.g. fedramp-moderate).

--location=LOCATION

The location of the Assured Workloads environment. For a current list of supported LOCATION values, see Assured Workloads locations.

--organization=ORGANIZATION

The parent organization of the Assured Workloads environment, provided as an organization ID.

Exactly one of these must be specified:

--new-folder-config=[PROPERTY=VALUE,…]

JSON/YAML specification for provisioning a new folder.

--new-project-config=[PROPERTY=VALUE,…]

JSON/YAML specification for provisioning a new project.

--target-folder=TARGET_FOLDER

Existing Folder ID to onboard into Assured Workloads.

--target-project=TARGET_PROJECT

Existing Project ID or project number to onboard into Assured Workloads.

OPTIONAL FLAGS

--async

Return immediately, without waiting for the operation in progress to complete.

--cmek-dedicated-project-config=[PROPERTY=VALUE,…]

Dedicated KMS project configuration (valid only with folder targets).

--cmek-key-ring=CMEK_KEY_RING

KMS Key Ring resource path for Customer-Managed Encryption Keys.

--description=DESCRIPTION

User-friendly description for the workload.

--framework-major-revision=FRAMEWORK_MAJOR_REVISION

Major revision ID of the compliance framework.

At most one of these can be specified:

--cloud-control-config=[PROPERTY=VALUE,…]

Repeated inline control configuration.

--cloud-control-configs-from-file=CLOUD_CONTROL_CONFIGS_FROM_FILE

Path to JSON/YAML file specifying multiple control configurations.

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 assured v2 workloads create

gcloud beta assured v2 workloads create