Yandex Cloud
Search
Contact UsGet started
  • Blog
  • Pricing
  • Documentation
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • ML & AI
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Customer Stories
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
    • Yandex Cloud Partner program
  • Blog
  • Pricing
  • Documentation
© 2025 Direct Cursus Technology L.L.C.
Yandex Serverless Containers
  • Comparison with other Yandex Cloud services
  • Access management
  • Pricing policy
  • Terraform reference
    • API authentication
      • Overview
        • Overview
        • Get
        • List
        • Create
        • Update
        • Delete
        • DeployRevision
        • Rollback
        • GetRevision
        • ListRevisions
        • ListOperations
        • ListAccessBindings
        • SetAccessBindings
        • UpdateAccessBindings
  • Audit Trails events
  • Release notes
  • FAQ

In this article:

  • gRPC request
  • RollbackContainerRequest
  • operation.Operation
  • RollbackContainerMetadata
  • Container
  1. Containers API reference
  2. gRPC
  3. Container
  4. Rollback

Serverless Containers Service, gRPC: ContainerService.Rollback

Written by
Yandex Cloud
Updated at January 14, 2025
  • gRPC request
  • RollbackContainerRequest
  • operation.Operation
  • RollbackContainerMetadata
  • Container

Rollback the specified container to an old revision.

gRPC requestgRPC request

rpc Rollback (RollbackContainerRequest) returns (operation.Operation)

RollbackContainerRequestRollbackContainerRequest

{
  "container_id": "string",
  "revision_id": "string"
}

Field

Description

container_id

string

Required field. ID of the container to rollback to an old revision.

To get a container ID, make a ContainerService.List request.

revision_id

string

Required field. ID of the revision to rollback to.

To get a revision ID make a ContainerService.ListRevisions request.

operation.Operationoperation.Operation

{
  "id": "string",
  "description": "string",
  "created_at": "google.protobuf.Timestamp",
  "created_by": "string",
  "modified_at": "google.protobuf.Timestamp",
  "done": "bool",
  "metadata": {
    "container_id": "string",
    "revision_id": "string"
  },
  // Includes only one of the fields `error`, `response`
  "error": "google.rpc.Status",
  "response": {
    "id": "string",
    "folder_id": "string",
    "created_at": "google.protobuf.Timestamp",
    "name": "string",
    "description": "string",
    "labels": "map<string, string>",
    "url": "string",
    "status": "Status"
  }
  // end of the list of possible fields
}

An Operation resource. For more information, see Operation.

Field

Description

id

string

ID of the operation.

description

string

Description of the operation. 0-256 characters long.

created_at

google.protobuf.Timestamp

Creation timestamp.

created_by

string

ID of the user or service account who initiated the operation.

modified_at

google.protobuf.Timestamp

The time when the Operation resource was last modified.

done

bool

If the value is false, it means the operation is still in progress.
If true, the operation is completed, and either error or response is available.

metadata

RollbackContainerMetadata

Service-specific metadata associated with the operation.
It typically contains the ID of the target resource that the operation is performed on.
Any method that returns a long-running operation should document the metadata type, if any.

error

google.rpc.Status

The error result of the operation in case of failure or cancellation.

Includes only one of the fields error, response.

The operation result.
If done == false and there was no failure detected, neither error nor response is set.
If done == false and there was a failure detected, error is set.
If done == true, exactly one of error or response is set.

response

Container

The normal response of the operation in case of success.
If the original method returns no data on success, such as Delete,
the response is google.protobuf.Empty.
If the original method is the standard Create/Update,
the response should be the target resource of the operation.
Any method that returns a long-running operation should document the response type, if any.

Includes only one of the fields error, response.

The operation result.
If done == false and there was no failure detected, neither error nor response is set.
If done == false and there was a failure detected, error is set.
If done == true, exactly one of error or response is set.

RollbackContainerMetadataRollbackContainerMetadata

Field

Description

container_id

string

ID of the container that is being rolled back.

revision_id

string

ID of the revision that the container is being rolled back to.

ContainerContainer

Field

Description

id

string

ID of the container. Generated at creation time.

folder_id

string

ID of the folder that the container belongs to.

created_at

google.protobuf.Timestamp

Creation timestamp for the container.

name

string

Name of the container. The name is unique within the folder.

description

string

Description of the container.

labels

object (map<string, string>)

Container labels as key:value pairs.

url

string

URL that needs to be requested to call the container.

status

enum Status

Status of the container.

  • STATUS_UNSPECIFIED
  • CREATING: Container is being created.
  • ACTIVE: Container is ready for use.
  • DELETING: Container is being deleted.
  • ERROR: Container failed. The only allowed action is delete.

Was the article helpful?

Previous
DeployRevision
Next
GetRevision
© 2025 Direct Cursus Technology L.L.C.