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.
This message has oneof_ fields (mutually exclusive fields).
For each oneof, at most one member field can be set at the same time.
Setting any member of the oneof automatically clears all other
members.
str
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'
create_time
google.protobuf.timestamp_pb2.Timestamp
Creation time of the rollout. Readonly.
Strategy that specifies how clients of Google Service Controller
want to send traffic to use different config versions. This is
generally used by API proxy to split traffic based on your
configured percentage for each config version.
One example of how to gradually rollout a new service configuration
using this strategy: Day 1
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-07 UTC."],[],[],null,["# Class Rollout (1.13.1)\n\nVersion latestkeyboard_arrow_down\n\n- [1.13.1 (latest)](/python/docs/reference/servicemanagement/latest/google.cloud.servicemanagement_v1.types.Rollout)\n- [1.13.0](/python/docs/reference/servicemanagement/1.13.0/google.cloud.servicemanagement_v1.types.Rollout)\n- [1.12.0](/python/docs/reference/servicemanagement/1.12.0/google.cloud.servicemanagement_v1.types.Rollout)\n- [1.11.0](/python/docs/reference/servicemanagement/1.11.0/google.cloud.servicemanagement_v1.types.Rollout)\n- [1.10.1](/python/docs/reference/servicemanagement/1.10.1/google.cloud.servicemanagement_v1.types.Rollout)\n- [1.8.5](/python/docs/reference/servicemanagement/1.8.5/google.cloud.servicemanagement_v1.types.Rollout)\n- [1.7.0](/python/docs/reference/servicemanagement/1.7.0/google.cloud.servicemanagement_v1.types.Rollout)\n- [1.6.1](/python/docs/reference/servicemanagement/1.6.1/google.cloud.servicemanagement_v1.types.Rollout)\n- [1.5.1](/python/docs/reference/servicemanagement/1.5.1/google.cloud.servicemanagement_v1.types.Rollout)\n- [1.4.0](/python/docs/reference/servicemanagement/1.4.0/google.cloud.servicemanagement_v1.types.Rollout)\n- [1.3.3](/python/docs/reference/servicemanagement/1.3.3/google.cloud.servicemanagement_v1.types.Rollout)\n- [1.2.3](/python/docs/reference/servicemanagement/1.2.3/google.cloud.servicemanagement_v1.types.Rollout)\n- [1.1.1](/python/docs/reference/servicemanagement/1.1.1/google.cloud.servicemanagement_v1.types.Rollout)\n- [1.0.4](/python/docs/reference/servicemanagement/1.0.4/google.cloud.servicemanagement_v1.types.Rollout)\n- [0.1.0](/python/docs/reference/servicemanagement/0.1.0/google.cloud.servicemanagement_v1.types.Rollout) \n\n Rollout(mapping=None, *, ignore_unknown_fields=False, **kwargs)\n\nA rollout resource that defines how service configuration\nversions are pushed to control plane systems. Typically, you\ncreate a new version of the service config, and then create a\nRollout to push the service config.\n\nThis message has `oneof`_ fields (mutually exclusive fields).\nFor each oneof, at most one member field can be set at the same time.\nSetting any member of the oneof automatically clears all other\nmembers.\n\n.. _oneof: \u003chttps://proto-plus-python.readthedocs.io/en/stable/fields.html#oneofs-mutually-exclusive-fields\u003e\n\nClasses\n-------\n\n### DeleteServiceStrategy\n\n DeleteServiceStrategy(mapping=None, *, ignore_unknown_fields=False, **kwargs)\n\nStrategy used to delete a service. This strategy is a\nplaceholder only used by the system generated rollout to delete\na service.\n\n### RolloutStatus\n\n RolloutStatus(value)\n\nStatus of a Rollout.\n\n### TrafficPercentStrategy\n\n TrafficPercentStrategy(mapping=None, *, ignore_unknown_fields=False, **kwargs)\n\nStrategy that specifies how clients of Google Service Controller\nwant to send traffic to use different config versions. This is\ngenerally used by API proxy to split traffic based on your\nconfigured percentage for each config version.\n\nOne example of how to gradually rollout a new service configuration\nusing this strategy: Day 1\n\n:: \n\n Rollout {\n id: \"example.googleapis.com/rollout_20160206\"\n traffic_percent_strategy {\n percentages: {\n \"example.googleapis.com/20160201\": 70.00\n \"example.googleapis.com/20160206\": 30.00\n }\n }\n }\n\nDay 2\n\n:: \n\n Rollout {\n id: \"example.googleapis.com/rollout_20160207\"\n traffic_percent_strategy: {\n percentages: {\n \"example.googleapis.com/20160206\": 100.00\n }\n }\n }"]]