You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ruby_cloud_description="Google Service Management allows service producers to publish their services on Google Cloud Platform so that they can be discovered and used by service consumers.",
// The full representation of a Service that is managed by
34
33
// Google Service Management.
35
34
messageManagedService {
36
-
// The name of the service. See the [overview](https://cloud.google.com/service-management/overview)
35
+
// The name of the service. See the [overview](/service-management/overview)
[services.undelete](/service-management/reference/rest/v1/services/undelete), to
66
+
[services.create](https://cloud.google.com/service-management/reference/rest/v1/services/create), [services.delete](https://cloud.google.com/service-management/reference/rest/v1/services/delete), [services.undelete](https://cloud.google.com/service-management/reference/rest/v1/services/undelete), to
Each managed service is described by a service configuration which covers
94
-
a wide range of features, including its name, title, RPC API
86
+
[here](https://cloud.google.com/service-management/reference/rest/v1/services.configs). Each
87
+
managed service is described by a service configuration which covers a
88
+
wide range of features, including its name, title, RPC API
95
89
definitions,
96
90
REST API definitions, documentation, authentication, and more.
97
91
@@ -102,8 +96,8 @@ documentation:
102
96
service configurations, making it possible to easily retrace how a
103
97
service's configuration evolved over time. Service configurations can be
104
98
published
105
-
using the [services.configs.create](/service-management/reference/rest/v1/services.configs/create) or
using the [services.configs.create](https://cloud.google.com/service-management/reference/rest/v1/services.configs/create) or
A `Rollout` defines how Google Service Management should deploy service
111
+
[here](https://cloud.google.com/service-management/reference/rest/v1/services.rollouts). A
112
+
`Rollout` defines how Google Service Management should deploy service
120
113
configurations to backend systems and how the configurations take effect
121
114
at runtime. It lets service producers specify multiple service
122
115
configuration
@@ -137,8 +130,7 @@ documentation:
137
130
Service Management keeps a history of rollouts so that service
138
131
producers can undo to previous configuration versions. You can rollback a
139
132
configuration by initiating a new `Rollout` that clones a previously
140
-
submitted
141
-
rollout record.
133
+
submitted rollout record.
142
134
rules:
143
135
- selector: google.iam.v1.IAMPolicy.GetIamPolicy
144
136
description: |-
@@ -150,14 +142,14 @@ documentation:
150
142
Sets the access control policy on the specified resource. Replaces
151
143
any existing policy.
152
144
153
-
Can return Public Errors: NOT_FOUND, INVALID_ARGUMENT and
154
-
PERMISSION_DENIED
145
+
Can return `NOT_FOUND`, `INVALID_ARGUMENT`, and `PERMISSION_DENIED`
0 commit comments