Hi there! Are you looking for the official Deno documentation? Try docs.deno.com for all your Deno learning needs.

AllocationPolicy

import type { AllocationPolicy } from "https://googleapis.deno.dev/v1/batch:v1.ts";

A Job's resource allocation policy describes when, where, and how compute resources should be allocated for the Job.

interface AllocationPolicy {
labels?: {
[key: string]: string;
}
;
location?: LocationPolicy;
network?: NetworkPolicy;
placement?: PlacementPolicy;
serviceAccount?: ServiceAccount;
tags?: string[];
}

§Properties

§

Describe instances that can be created by this AllocationPolicy. Only instances[0] is supported now.

§
labels?: {
[key: string]: string;
}
[src]

Custom labels to apply to the job and all the Compute Engine resources that both are created by this allocation policy and support labels. Use labels to group and describe the resources they are applied to. Batch automatically applies predefined labels and supports multiple labels fields for each job, which each let you apply custom labels to various resources. Label names that start with "goog-" or "google-" are reserved for predefined labels. For more information about labels with Batch, see Organize resources using labels.

§

Location where compute resources should be allocated for the Job.

§

The network policy. If you define an instance template in the InstancePolicyOrTemplate field, Batch will use the network settings in the instance template instead of this field.

§

The placement policy.

§
serviceAccount?: ServiceAccount
[src]

Defines the service account for Batch-created VMs. If omitted, the default Compute Engine service account is used. Must match the service account specified in any used instance template configured in the Batch job. Includes the following fields: * email: The service account's email address. If not set, the default Compute Engine service account is used. * scopes: Additional OAuth scopes to grant the service account, beyond the default cloud-platform scope. (list of strings)

§
tags?: string[]
[src]

Optional. Tags applied to the VM instances. The tags identify valid sources or targets for network firewalls. Each tag must be 1-63 characters long, and comply with RFC1035.