Post v1servicesservicenamerollouts — servicemanagement

v1

latestOpenAPI 3.0.0Creative Commons Attribution 3.02026-07-1319110171.7 KB

services

Creates a new service configuration rollout. Based on rollout, the Google Service Management will roll out the service configurations to different backend services. For example, the logging configuration will be pushed to Google Cloud Logging. Please note that any previous pending and running Rollouts and associated Operations will be automatically cancelled so that the latest Rollout will not be blocked by previous Rollouts. Only the 100 most recent (in any state) and the last 10 successful (if not already part of the set of 100 most recent) rollouts are kept for each service. The rest will be deleted eventually. Operation

post/v1/services/{serviceName}/rollouts

Path parameters

serviceNamestring required

Required. The name of the service. See the overview for naming requirements. For example: example.googleapis.com.

Request body

rolloutIdstring

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'

serviceNamestring

The name of the service associated with this Rollout.

createTimestring google-datetime

Creation time of the rollout. Readonly.

deleteServiceStrategyDeleteServiceStrategy

Strategy used to delete a service. This strategy is a placeholder only used by the system generated rollout to delete a service.

createdBystring

The user who created the Rollout. Readonly.

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

Response

Successful response