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
## Deleted keys were detected in the following stable discovery artifacts:
documentai v1 222030d
serviceconsumermanagement v1 e204636
serviceusage v1 b79b21e
## Deleted keys were detected in the following pre-stable discovery artifacts:
firebase v1beta1 6bd0412
serviceconsumermanagement v1beta1 e204636
serviceusage v1beta1 b79b21e
## Discovery Artifact Change Summary:
feat(apigee): update the api 37f3142
feat(container): update the api 514acdb
feat(dlp): update the api 7e3d1c4
feat(documentai): update the api 222030d
feat(firebase): update the api 6bd0412
feat(ondemandscanning): update the api b77d12d
feat(osconfig): update the api c541143
feat(prod_tt_sasportal): update the api 1e0f4a6
feat(serviceconsumermanagement): update the api e204636
feat(serviceusage): update the api b79b21e
Copy file name to clipboardExpand all lines: docs/dyn/apigee_v1.organizations.apis.deployments.html
+1Lines changed: 1 addition & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -162,6 +162,7 @@ <h3>Method Details</h3>
162
162
"environmentGroup": "A String", # Name of the environment group in which this conflict exists.
163
163
},
164
164
],
165
+
"serviceAccount": "A String", # The full resource name of Cloud IAM Service Account that this deployment is using, eg, `projects/-/serviceAccounts/{email}`.
165
166
"state": "A String", # Current state of the deployment. This field is not populated in List APIs.
Copy file name to clipboardExpand all lines: docs/dyn/apigee_v1.organizations.apis.revisions.deployments.html
+1Lines changed: 1 addition & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -162,6 +162,7 @@ <h3>Method Details</h3>
162
162
"environmentGroup": "A String", # Name of the environment group in which this conflict exists.
163
163
},
164
164
],
165
+
"serviceAccount": "A String", # The full resource name of Cloud IAM Service Account that this deployment is using, eg, `projects/-/serviceAccounts/{email}`.
165
166
"state": "A String", # Current state of the deployment. This field is not populated in List APIs.
Copy file name to clipboardExpand all lines: docs/dyn/apigee_v1.organizations.deployments.html
+1Lines changed: 1 addition & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -163,6 +163,7 @@ <h3>Method Details</h3>
163
163
"environmentGroup": "A String", # Name of the environment group in which this conflict exists.
164
164
},
165
165
],
166
+
"serviceAccount": "A String", # The full resource name of Cloud IAM Service Account that this deployment is using, eg, `projects/-/serviceAccounts/{email}`.
166
167
"state": "A String", # Current state of the deployment. This field is not populated in List APIs.
Copy file name to clipboardExpand all lines: docs/dyn/apigee_v1.organizations.developers.apps.keys.apiproducts.html
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -82,7 +82,7 @@ <h2>Instance Methods</h2>
82
82
<pclass="firstline">Removes an API product from an app's consumer key. After the API product is removed, the app cannot access the API resources defined in that API product. **Note**: The consumer key is not removed, only its association with the API product.</p>
<pclass="firstline">Approve or revoke an app's consumer key. After a consumer key is approved, the app can use it to access APIs. A consumer key that is revoked or pending cannot be used to access an API. Any access tokens associated with a revoked consumer key will remain active. However, Apigee hybrid checks the status of the consumer key and if set to `revoked` will not allow access to the API.</p>
85
+
<pclass="firstline">Approves or revokes the consumer key for an API product. After a consumer key is approved, the app can use it to access APIs. A consumer key that is revoked or pending cannot be used to access an API. Any access tokens associated with a revoked consumer key will remain active. However, Apigee checks the status of the consumer key and if set to `revoked` will not allow access to the API.</p>
<pre>Approve or revoke an app's consumer key. After a consumer key is approved, the app can use it to access APIs. A consumer key that is revoked or pending cannot be used to access an API. Any access tokens associated with a revoked consumer key will remain active. However, Apigee hybrid checks the status of the consumer key and if set to `revoked` will not allow access to the API.
130
+
<pre>Approves or revokes the consumer key for an API product. After a consumer key is approved, the app can use it to access APIs. A consumer key that is revoked or pending cannot be used to access an API. Any access tokens associated with a revoked consumer key will remain active. However, Apigee checks the status of the consumer key and if set to `revoked` will not allow access to the API.
131
131
132
132
Args:
133
133
name: string, Name of the API product in the developer app key in the following format: `organizations/{org}/developers/{developer_email}/apps/{app}/keys/{key}/apiproducts/{apiproduct}` (required)
<pclass="firstline">Creates a custom consumer key and secret for a developer app. This is particularly useful if you want to migrate existing consumer keys and secrets to Apigee hybrid from another system. Consumer keys and secrets can contain letters, numbers, underscores, and hyphens. No other special characters are allowed. To avoid service disruptions, a consumer key and secret should not exceed 2 KBs each. **Note**: When creating the consumer key and secret, an association to API products will not be made. Therefore, you should not specify the associated API products in your request. Instead, use the UpdateDeveloperAppKey API to make the association after the consumer key and secret are created. If a consumer key and secret already exist, you can keep them or delete them using the DeleteDeveloperAppKey API.</p>
82
+
<pclass="firstline">Creates a custom consumer key and secret for a developer app. This is particularly useful if you want to migrate existing consumer keys and secrets to Apigee from another system. Consumer keys and secrets can contain letters, numbers, underscores, and hyphens. No other special characters are allowed. To avoid service disruptions, a consumer key and secret should not exceed 2 KBs each. **Note**: When creating the consumer key and secret, an association to API products will not be made. Therefore, you should not specify the associated API products in your request. Instead, use the UpdateDeveloperAppKey API to make the association after the consumer key and secret are created. If a consumer key and secret already exist, you can keep them or delete them using the DeleteDeveloperAppKey API.</p>
<pre>Creates a custom consumer key and secret for a developer app. This is particularly useful if you want to migrate existing consumer keys and secrets to Apigee hybrid from another system. Consumer keys and secrets can contain letters, numbers, underscores, and hyphens. No other special characters are allowed. To avoid service disruptions, a consumer key and secret should not exceed 2 KBs each. **Note**: When creating the consumer key and secret, an association to API products will not be made. Therefore, you should not specify the associated API products in your request. Instead, use the UpdateDeveloperAppKey API to make the association after the consumer key and secret are created. If a consumer key and secret already exist, you can keep them or delete them using the DeleteDeveloperAppKey API.
91
+
<pre>Creates a custom consumer key and secret for a developer app. This is particularly useful if you want to migrate existing consumer keys and secrets to Apigee from another system. Consumer keys and secrets can contain letters, numbers, underscores, and hyphens. No other special characters are allowed. To avoid service disruptions, a consumer key and secret should not exceed 2 KBs each. **Note**: When creating the consumer key and secret, an association to API products will not be made. Therefore, you should not specify the associated API products in your request. Instead, use the UpdateDeveloperAppKey API to make the association after the consumer key and secret are created. If a consumer key and secret already exist, you can keep them or delete them using the DeleteDeveloperAppKey API.
92
92
93
93
Args:
94
94
parent: string, Parent of the developer app key. Use the following structure in your request: `organizations/{org}/developers/{developer_email}/apps` (required)
Copy file name to clipboardExpand all lines: docs/dyn/apigee_v1.organizations.developers.apps.keys.html
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -92,7 +92,7 @@ <h2>Instance Methods</h2>
92
92
<pclass="firstline">Deletes an app's consumer key and removes all API products associated with the app. After the consumer key is deleted, it cannot be used to access any APIs. **Note**: After you delete a consumer key, you may want to: 1. Create a new consumer key and secret for the developer app using the CreateDeveloperAppKey API, and subsequently add an API product to the key using the UpdateDeveloperAppKey API. 2. Delete the developer app, if it is no longer required.</p>
<pclass="firstline">Returns details for a consumer key for a developer app, including the key and secret value, associated API products, and other information.</p>
95
+
<pclass="firstline">Gets details for a consumer key for a developer app, including the key and secret value, associated API products, and other information.</p>
<pclass="firstline">Updates the scope of an app. This API replaces the existing scopes with those specified in the request. Include or exclude any existing scopes that you want to retain or delete, respectively. The specified scopes must already be defined for the API products associated with the app. This API sets the `scopes` element under the `apiProducts` element in the attributes of the app.</p>
<pre>Returns details for a consumer key for a developer app, including the key and secret value, associated API products, and other information.
146
+
<pre>Gets details for a consumer key for a developer app, including the key and secret value, associated API products, and other information.
147
147
148
148
Args:
149
149
name: string, Name of the developer app key. Use the following structure in your request: `organizations/{org}/developers/{developer_email}/apps/{app}/keys/{key}` (required)
Copy file name to clipboardExpand all lines: docs/dyn/apigee_v1.organizations.environments.apis.deployments.html
+1Lines changed: 1 addition & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -162,6 +162,7 @@ <h3>Method Details</h3>
162
162
"environmentGroup": "A String", # Name of the environment group in which this conflict exists.
163
163
},
164
164
],
165
+
"serviceAccount": "A String", # The full resource name of Cloud IAM Service Account that this deployment is using, eg, `projects/-/serviceAccounts/{email}`.
165
166
"state": "A String", # Current state of the deployment. This field is not populated in List APIs.
<pclass="firstline">Deploys a revision of an API proxy. If another revision of the same API proxy revision is currently deployed, set the `override` parameter to `true` to have this revision replace the currently deployed revision. You cannot invoke an API proxy until it has been deployed to an environment. After you deploy an API proxy revision, you cannot edit it. To edit the API proxy, you must create and deploy a new revision. For a request path `organizations/{org}/environments/{env}/apis/{api}/revisions/{rev}/deployments`, two permissions are required: * `apigee.deployments.create` on the resource `organizations/{org}/environments/{env}` * `apigee.proxyrevisions.deploy` on the resource `organizations/{org}/apis/{api}/revisions/{rev}` </p>
<pre>Deploys a revision of an API proxy. If another revision of the same API proxy revision is currently deployed, set the `override` parameter to `true` to have this revision replace the currently deployed revision. You cannot invoke an API proxy until it has been deployed to an environment. After you deploy an API proxy revision, you cannot edit it. To edit the API proxy, you must create and deploy a new revision. For a request path `organizations/{org}/environments/{env}/apis/{api}/revisions/{rev}/deployments`, two permissions are required: * `apigee.deployments.create` on the resource `organizations/{org}/environments/{env}` * `apigee.proxyrevisions.deploy` on the resource `organizations/{org}/apis/{api}/revisions/{rev}`
108
108
109
109
Args:
110
110
name: string, Required. Name of the API proxy revision deployment in the following format: `organizations/{org}/environments/{env}/apis/{api}/revisions/{rev}` (required)
111
111
override: boolean, Flag that specifies whether the new deployment replaces other deployed revisions of the API proxy in the environment. Set `override` to `true` to replace other deployed revisions. By default, `override` is `false` and the deployment is rejected if other revisions of the API proxy are deployed in the environment.
112
112
sequencedRollout: boolean, Flag that specifies whether to enable sequenced rollout. If set to `true`, a best-effort attempt will be made to roll out the routing rules corresponding to this deployment and the environment changes to add this deployment in a safe order. This reduces the risk of downtime that could be caused by changing the environment group's routing before the new destination for the affected traffic is ready to receive it. This should only be necessary if the new deployment will be capturing traffic from another environment under a shared environment group or if traffic will be rerouted to a different environment due to a base path removal. The [GenerateDeployChangeReport API](GenerateDeployChangeReport) may be used to examine routing changes before issuing the deployment request, and its response will indicate if a sequenced rollout is recommended for the deployment.
113
+
serviceAccount: string, Google Cloud IAM service account. The service account represents the identity of the deployed proxy, and determines what permissions it has. The format must be `{ACCOUNT_ID}@{PROJECT}.iam.gserviceaccount.com`.
113
114
x__xgafv: string, V1 error format.
114
115
Allowed values
115
116
1 - v1 error format
@@ -178,6 +179,7 @@ <h3>Method Details</h3>
178
179
"environmentGroup": "A String", # Name of the environment group in which this conflict exists.
179
180
},
180
181
],
182
+
"serviceAccount": "A String", # The full resource name of Cloud IAM Service Account that this deployment is using, eg, `projects/-/serviceAccounts/{email}`.
181
183
"state": "A String", # Current state of the deployment. This field is not populated in List APIs.
182
184
}</pre>
183
185
</div>
@@ -256,6 +258,7 @@ <h3>Method Details</h3>
256
258
"environmentGroup": "A String", # Name of the environment group in which this conflict exists.
257
259
},
258
260
],
261
+
"serviceAccount": "A String", # The full resource name of Cloud IAM Service Account that this deployment is using, eg, `projects/-/serviceAccounts/{email}`.
259
262
"state": "A String", # Current state of the deployment. This field is not populated in List APIs.
Copy file name to clipboardExpand all lines: docs/dyn/apigee_v1.organizations.environments.deployments.html
+1Lines changed: 1 addition & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -163,6 +163,7 @@ <h3>Method Details</h3>
163
163
"environmentGroup": "A String", # Name of the environment group in which this conflict exists.
164
164
},
165
165
],
166
+
"serviceAccount": "A String", # The full resource name of Cloud IAM Service Account that this deployment is using, eg, `projects/-/serviceAccounts/{email}`.
166
167
"state": "A String", # Current state of the deployment. This field is not populated in List APIs.
0 commit comments