Struct InstanceTemplateArgs

pub struct InstanceTemplateArgs {

    pub advanced_machine_features: Output<Option<InstanceTemplateAdvancedMachineFeatures>>,
    pub can_ip_forward: Output<Option<bool>>,
    pub confidential_instance_config: Output<Option<InstanceTemplateConfidentialInstanceConfig>>,
    pub description: Output<Option<String>>,
    pub disks: Output<Vec<InstanceTemplateDisk>>,
    pub enable_display: Output<Option<bool>>,
    pub guest_accelerators: Output<Option<Vec<InstanceTemplateGuestAccelerator>>>,
    pub instance_description: Output<Option<String>>,
    pub key_revocation_action_type: Output<Option<String>>,
    pub labels: Output<Option<HashMap<String, String>>>,
    pub machine_type: Output<String>,
    pub metadata: Output<Option<HashMap<String, String>>>,
    pub metadata_startup_script: Output<Option<String>>,
    pub min_cpu_platform: Output<Option<String>>,
    pub name: Output<Option<String>>,
    pub name_prefix: Output<Option<String>>,
    pub network_interfaces: Output<Option<Vec<InstanceTemplateNetworkInterface>>>,
    pub network_performance_config: Output<Option<InstanceTemplateNetworkPerformanceConfig>>,
    pub partner_metadata: Output<Option<HashMap<String, String>>>,
    pub project: Output<Option<String>>,
    pub region: Output<Option<String>>,
    pub reservation_affinity: Output<Option<InstanceTemplateReservationAffinity>>,
    pub resource_manager_tags: Output<Option<HashMap<String, String>>>,
    pub resource_policies: Output<Option<String>>,
    pub scheduling: Output<Option<InstanceTemplateScheduling>>,
    pub service_account: Output<Option<InstanceTemplateServiceAccount>>,
    pub shielded_instance_config: Output<Option<InstanceTemplateShieldedInstanceConfig>>,
    pub tags: Output<Option<Vec<String>>>,
}

Fields

advanced_machine_features: Output<Option<InstanceTemplateAdvancedMachineFeatures>>

Configure Nested Virtualisation and Simultaneous Hyper Threading on this VM. Structure is documented below

can_ip_forward: Output<Option<bool>>

Whether to allow sending and receiving of packets with non-matching source or destination IPs. This defaults to false.

confidential_instance_config: Output<Option<InstanceTemplateConfidentialInstanceConfig>>

Enable Confidential Mode on this VM. Structure is documented below

description: Output<Option<String>>

A brief description of this resource.

disks: Output<Vec<InstanceTemplateDisk>>

Disks to attach to instances created from this template. This can be specified multiple times for multiple disks. Structure is documented below.

enable_display: Output<Option<bool>>

Enable Virtual Displays on this instance. Note: allow_stopping_for_update must be set to true in order to update this field.

guest_accelerators: Output<Option<Vec<InstanceTemplateGuestAccelerator>>>

List of the type and count of accelerator cards attached to the instance. Structure documented below.

instance_description: Output<Option<String>>

A brief description to use for instances created from this template.

key_revocation_action_type: Output<Option<String>>

Action to be taken when a customer’s encryption key is revoked. Supports STOP and NONE, with NONE being the default.

labels: Output<Option<HashMap<String, String>>>

A set of key/value label pairs to assign to instances created from this template.

Note: This field is non-authoritative, and will only manage the labels present in your configuration. Please refer to the field ‘effective_labels’ for all of the labels present on the resource.

machine_type: Output<String>

The machine type to create.

To create a machine with a custom type (such as extended memory), format the value like custom-VCPUS-MEM_IN_MB like custom-6-20480 for 6 vCPU and 20GB of RAM.

---

metadata: Output<Option<HashMap<String, String>>>

Metadata key/value pairs to make available from within instances created from this template.

metadata_startup_script: Output<Option<String>>

An alternative to using the startup-script metadata key, mostly to match the compute_instance resource. This replaces the startup-script metadata key on the created instance and thus the two mechanisms are not allowed to be used simultaneously.

min_cpu_platform: Output<Option<String>>

Specifies a minimum CPU platform. Applicable values are the friendly names of CPU platforms, such as Intel Haswell or Intel Skylake. See the complete list here.

name: Output<Option<String>>

The name of the instance template. If you leave this blank, the provider will auto-generate a unique name.

name_prefix: Output<Option<String>>

Creates a unique name beginning with the specified prefix. Conflicts with name. Max length is 54 characters. Prefixes with lengths longer than 37 characters will use a shortened UUID that will be more prone to collisions.

Resulting name for a name_prefix <= 37 characters: name_prefix + YYYYmmddHHSSssss + 8 digit incremental counter Resulting name for a name_prefix 38 - 54 characters: name_prefix + YYmmdd + 3 digit incremental counter

network_interfaces: Output<Option<Vec<InstanceTemplateNetworkInterface>>>

Networks to attach to instances created from this template. This can be specified multiple times for multiple networks. Structure is documented below.

network_performance_config: Output<Option<InstanceTemplateNetworkPerformanceConfig>>

(Optional, Configures network performance settings for the instance created from the template. Structure is documented below. Note: machine_type must be a supported type, the image used must include the GVNIC in guest-os-features, and network_interface.0.nic-type must be GVNIC in order for this setting to take effect.

partner_metadata: Output<Option<HashMap<String, String>>>

Beta key/value pair represents partner metadata assigned to instance template where key represent a defined namespace and value is a json string represent the entries associted with the namespace.

project: Output<Option<String>>

The ID of the project in which the resource belongs. If it is not provided, the provider project is used.

region: Output<Option<String>>

An instance template is a global resource that is not bound to a zone or a region. However, you can still specify some regional resources in an instance template, which restricts the template to the region where that resource resides. For example, a custom subnetwork resource is tied to a specific region. Defaults to the region of the Provider if no value is given.

reservation_affinity: Output<Option<InstanceTemplateReservationAffinity>>

Specifies the reservations that this instance can consume from. Structure is documented below.

resource_manager_tags: Output<Option<HashMap<String, String>>>

A set of key/value resource manager tag pairs to bind to the instances. Keys must be in the format tagKeys/{tag_key_id}, and values are in the format tagValues/456.

resource_policies: Output<Option<String>>

• A list of self_links of resource policies to attach to the instance. Modifying this list will cause the instance to recreate. Currently a max of 1 resource policy is supported.

scheduling: Output<Option<InstanceTemplateScheduling>>

The scheduling strategy to use. More details about this configuration option are detailed below.

service_account: Output<Option<InstanceTemplateServiceAccount>>

Service account to attach to the instance. Structure is documented below.

shielded_instance_config: Output<Option<InstanceTemplateShieldedInstanceConfig>>

Enable Shielded VM on this instance. Shielded VM provides verifiable integrity to prevent against malware and rootkits. Defaults to disabled. Structure is documented below. Note: shielded_instance_config can only be used with boot images with shielded vm support. See the complete list here.

tags: Output<Option<Vec<String>>>

Tags to attach to the instance.

Implementations

impl InstanceTemplateArgs

pub fn builder() -> InstanceTemplateArgsBuilder

Create an instance of InstanceTemplateArgs using the builder syntax

Trait Implementations

impl Clone for InstanceTemplateArgs

fn clone(&self) -> InstanceTemplateArgs

Returns a copy of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.