Rollout

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

A rollout resource that defines how service configuration versions are pushed to control plane systems. Typically, you create a new version of the service config, and then create a Rollout to push the service config.

interface Rollout {

createdBy?: string;

createTime?: Date;

deleteServiceStrategy?: DeleteServiceStrategy;

rolloutId?: string;

serviceName?: string;

status?:

| "ROLLOUT_STATUS_UNSPECIFIED"

| "IN_PROGRESS"

| "SUCCESS"

| "CANCELLED"

| "FAILED"

| "PENDING"

| "FAILED_ROLLED_BACK";

trafficPercentStrategy?: TrafficPercentStrategy;

}

§Properties

createdBy?: string

[src]

The user who created the Rollout. Readonly.

createTime?: Date

[src]

Creation time of the rollout. Readonly.

deleteServiceStrategy?: DeleteServiceStrategy

[src]

The strategy associated with a rollout to delete a ManagedService. Readonly.

rolloutId?: string

[src]

Optional. Unique identifier of this Rollout. Must be no longer than 63 characters and only lower case letters, digits, '.', '_' and '-' are allowed. If not specified by client, the server will generate one. The generated id will have the form of , where "date" is the create date in ISO 8601 format. "revision number" is a monotonically increasing positive number that is reset every day for each service. An example of the generated rollout_id is '2016-02-16r1'

serviceName?: string

[src]

The name of the service associated with this Rollout.

[src]

The status of this rollout. Readonly. In case of a failed rollout, the system will automatically rollback to the current Rollout version. Readonly.

trafficPercentStrategy?: TrafficPercentStrategy

[src]

Google Service Control selects service configurations based on traffic percentage.