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

CreateComponentRequest

import type { CreateComponentRequest } from "https://aws-api.deno.dev/v0.4/services/imagebuilder.ts?docs=full";
interface CreateComponentRequest {
changeDescription?: string | null;
clientToken: string;
data?: string | null;
description?: string | null;
kmsKeyId?: string | null;
name: string;
platform: Platform;
semanticVersion: string;
supportedOsVersions?: string[] | null;
tags?: {
[key: string]: string | null | undefined;
}
| null;
uri?: string | null;
}

§Properties

§
changeDescription?: string | null
[src]

The change description of the component. Describes what change has been made in this version, or what makes this version different from other versions of this component.

§
clientToken: string
[src]

The idempotency token of the component.

§
data?: string | null
[src]

Component data contains inline YAML document content for the component. Alternatively, you can specify the uri of a YAML document file stored in Amazon S3. However, you cannot specify both properties.

§
description?: string | null
[src]

Describes the contents of the component.

§
kmsKeyId?: string | null
[src]

The ID of the KMS key that is used to encrypt this component.

§
name: string
[src]

The name of the component.

§
platform: Platform
[src]

The operating system platform of the component.

§
semanticVersion: string
[src]

The semantic version of the component. This version follows the semantic version syntax.

Note: The semantic version has four nodes: ../. You can assign values for the first three, and can filter on all of them. Assignment: For the first three nodes you can assign any positive integer value, including zero, with an upper limit of 2^30-1, or 1073741823 for each node. Image Builder automatically assigns the build number to the fourth node. Patterns: You can use any numeric pattern that adheres to the assignment requirements for the nodes that you can assign. For example, you might choose a software version pattern, such as 1.0.0, or a date, such as 2021.01.01.

§
supportedOsVersions?: string[] | null
[src]

The operating system (OS) version supported by the component. If the OS information is available, a prefix match is performed against the base image OS version during image recipe creation.

§
tags?: {
[key: string]: string | null | undefined;
}
| null
[src]

The tags that apply to the component.

§
uri?: string | null
[src]

The uri of a YAML component document file. This must be an S3 URL (s3://bucket/key), and the requester must have permission to access the S3 bucket it points to. If you use Amazon S3, you can specify component content up to your service quota.

Alternatively, you can specify the YAML document inline, using the component data property. You cannot specify both properties.