Method: revisions.rollback

• HTTP request
• Path parameters
• Request body
• Response body
• Authorization scopes
• IAM Permissions

Full name: projects.locations.instances.integrations.managers.revisions.rollback

Reverts the current manager definition to a previously saved revision. Use this method to rapidly recover a functional state for common code if an update causes operational issues in dependent actions or jobs.

HTTP request

Choose a location:

africa-south1 asia-northeast1 asia-south1 asia-southeast1 asia-southeast2 australia-southeast1 europe-central2 europe-west12 europe-west2 europe-west3 europe-west6 europe-west9 me-central1 me-central2 me-west1 northamerica-northeast2 southamerica-east1 us eu

POST https://chronicle.africa-south1.rep.googleapis.com/v1alpha/{name}:rollback

Path parameters

Parameters
name	string Required. The resource name of the IntegrationManagerRevision to rollback. Format: projects/{project}/locations/{location}/instances/{instance}/integrations/{integration}/managers/{manager}/revisions/{revision}:rollback

Request body

The request body must be empty.

Response body

If successful, the response body contains an instance of IntegrationManagerRevision.

Authorization scopes

Requires one of the following OAuth scopes:

• https://www.googleapis.com/auth/cloud-platform
• https://www.googleapis.com/auth/chronicle
• https://www.googleapis.com/auth/chronicle.readonly

For more information, see the Authentication Overview.

IAM Permissions

Requires the following IAM permission on the name resource:

• chronicle.managerRevisions.update

For more information, see the IAM documentation.