ccictl rollout history

Scenario

View the previous revisions and configurations that have been brought online.

ccictl rollout history (TYPE NAME | TYPE/NAME) [flags]

Examples

# View the rollout history of a Deployment.
ccictl rollout history deployment/abc

# View the details about revision 3 of the Deployment.
ccictl rollout history deployment/abc --revision=3

Options

--allow-missing-template-keys     Default: true

If the value is true, the error in the template is ignored when a field or mapping key is missing in the template. This option applies only to the Golang and JSONPath output formats.

-f, --filename strings

List of file names, directories, or file URLs, which are used to identify the resource to be obtained from the server.

-h, --help

Help information for rollout history

-o, --output string

Output format. The value options include json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, and jsonpath-file.

-R, --recursive

Process the directory used in -f or --filename recursively. This option is useful when you want to manage related manifests organized within the same directory.

--revision int

View details, including the pod template of the specified revision.

-l, --selector string

Selector used for filtering (label query). The value can be =, ==, or !=, for example, -l key1=value1,key2=value2. Matched objects must meet all specified label constraints.

--template string

Template character string or template file path used when -o is set to go-template or go-template-file. The Golang template format is [http://golang.org/pkg/text/template/#pkg-overview].

The following ccictl options can also be used in subcommands:

Parent command options