ProvisioningConfigArgs constructor

const ProvisioningConfigArgs({ Input<String>? customId, Input<String>? email, Input<String>? handoverServiceAccount, Input<List<InstanceConfig>>? instances, Input<String>? location, Input<List<NetworkConfig>>? networks, Input<String>? pod, Input<String>? project, Input<String>? statusMessage, Input<String>? ticketId, Input<List<VolumeConfig>>? volumes, Input<bool>? vpcScEnabled, })

Creates a new ProvisioningConfigArgs. customId Optional. The user-defined identifier of the provisioning config. email Email provided to send a confirmation with provisioning config to. Deprecated in favour of email field in request messages. handoverServiceAccount A service account to enable customers to access instance credentials upon handover. instances Instances to be created. location Optional. Location name of this ProvisioningConfig. It is optional only for Intake UI transition period. networks Networks to be created. pod Optional. Pod name. Pod is an independent part of infrastructure. Instance can be connected to the assets (networks, volumes, nfsshares) allocated in the same pod only. project Optional. statusMessage Optional status messages associated with the FAILED state. ticketId A generated ticket id to track provisioning request. volumes Volumes to be created. vpcScEnabled If true, VPC SC is enabled for the cluster.

Implementation

const ProvisioningConfigArgs({
  this.customId,
  this.email,
  this.handoverServiceAccount,
  this.instances,
  this.location,
  this.networks,
  this.pod,
  this.project,
  this.statusMessage,
  this.ticketId,
  this.volumes,
  this.vpcScEnabled,
});