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
Copy file name to clipboardExpand all lines: docs/dyn/apigee_v1.organizations.apis.revisions.html
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -87,7 +87,7 @@ <h2>Instance Methods</h2>
87
87
<pclass="firstline">Deletes an API proxy revision and all policies, resources, endpoints, and revisions associated with it. The API proxy revision must be undeployed before you can delete it.</p>
<pclass="firstline">Gets an API proxy revision. To download the API proxy configuration bundle for the specified revision as a zip file, do the following: * Set the `format` query parameter to `bundle`. * Set the `Accept` header to `application/zip`. If you are using curl, specify `-o filename.zip` to save the output to a file; otherwise, it displays to `stdout`. Then, develop the API proxy configuration locally and upload the updated API proxy configuration revision, as described in [updateApiProxyRevision](updateApiProxyRevision).</p>
90
+
<pclass="firstline">Gets an API proxy revision. To download the API proxy configuration bundle for the specified revision as a zip file, set the `format` query parameter to `bundle`. If you are using curl, specify `-o filename.zip` to save the output to a file; otherwise, it displays to `stdout`. Then, develop the API proxy configuration locally and upload the updated API proxy configuration revision, as described in [updateApiProxyRevision](updateApiProxyRevision).</p>
<pclass="firstline">Updates an existing API proxy revision by uploading the API proxy configuration bundle as a zip file from your local machine. You can update only API proxy revisions that have never been deployed. After deployment, an API proxy revision becomes immutable, even if it is undeployed. Set the `Content-Type` header to either `multipart/form-data` or `application/octet-stream`.</p>
<pre>Gets an API proxy revision. To download the API proxy configuration bundle for the specified revision as a zip file, do the following: * Set the `format` query parameter to `bundle`. * Set the `Accept` header to `application/zip`. If you are using curl, specify `-o filename.zip` to save the output to a file; otherwise, it displays to `stdout`. Then, develop the API proxy configuration locally and upload the updated API proxy configuration revision, as described in [updateApiProxyRevision](updateApiProxyRevision).
174
+
<pre>Gets an API proxy revision. To download the API proxy configuration bundle for the specified revision as a zip file, set the `format` query parameter to `bundle`. If you are using curl, specify `-o filename.zip` to save the output to a file; otherwise, it displays to `stdout`. Then, develop the API proxy configuration locally and upload the updated API proxy configuration revision, as described in [updateApiProxyRevision](updateApiProxyRevision).
175
175
176
176
Args:
177
177
name: string, Required. API proxy revision in the following format: `organizations/{org}/apis/{api}/revisions/{rev}` (required)
<pclass="firstline">Get a list of metrics and dimensions which can be used for creating analytics queries and reports. Each schema element contains the name of the field with its associated type and if it is either custom field or standard field.</p>
<pclass="firstline">Gets a list of metrics and dimensions that can be used to create analytics queries and reports. Each schema element contains the name of the field, its associated type, and a flag indicating whether it is a standard or custom field.</p>
<pre>Get a list of metrics and dimensions which can be used for creating analytics queries and reports. Each schema element contains the name of the field with its associated type and if it is either custom field or standard field.
<pre>Gets a list of metrics and dimensions that can be used to create analytics queries and reports. Each schema element contains the name of the field, its associated type, and a flag indicating whether it is a standard or custom field.
92
92
93
93
Args:
94
-
name: string, Required. The parent organization and environment names. Must be of the form `organizations/{org}/environments/{env}/analytics/admin/schemav2`. (required)
95
-
type: string, Required. Type refers to the dataset name whose schema needs to be retrieved E.g. type=fact or type=agg_cus1
94
+
name: string, Required. Path to the schema. Use the following structure in your request: `organizations/{org}/environments/{env}/analytics/admin/schemav2`. (required)
95
+
disableCache: boolean, Flag that specifies whether the schema is be read from the database or cache. Set to `true` to read the schema from the database. Defaults to cache.
96
+
type: string, Required. Name of the dataset for which you want to retrieve the schema. For example: `fact` or `agg_cus1`
96
97
x__xgafv: string, V1 error format.
97
98
Allowed values
98
99
1 - v1 error format
@@ -102,25 +103,25 @@ <h3>Method Details</h3>
102
103
An object of the form:
103
104
104
105
{ # Response for Schema call
105
-
"dimensions": [ # List of schema fiels grouped as dimensions.
106
+
"dimensions": [ # List of schema fields grouped as dimensions.
106
107
{ # Message type for the schema element
107
-
"name": "A String", # Name of the field
108
-
"properties": { # Message type for schema property # Property of the schema field E.g. { "createTime": "2016-02-26T10:23:09.592Z", "custom": "false", "type": "string" }
109
-
"createTime": "A String", # Creation time of the field
110
-
"custom": "A String", # Custom is a flag signifying if the field was provided as part of the standard dataset or a custom field created by the customer
108
+
"name": "A String", # Name of the field.
109
+
"properties": { # Properties for the schema field. # Properties for the schema field. For example: { "createTime": "2016-02-26T10:23:09.592Z", "custom": "false", "type": "string" }
110
+
"createTime": "A String", # Time the field was created in RFC3339 string form. For example: `2016-02-26T10:23:09.592Z`.
111
+
"custom": "A String", # Flag that specifies whether the field is standard in the dataset or a custom field created by the customer. `true` indicates that it is a custom field.
111
112
"type": "A String", # Data type of the field.
112
113
},
113
114
},
114
115
],
115
116
"meta": [ # Additional metadata associated with schema. This is a legacy field and usually consists of an empty array of strings.
116
117
"A String",
117
118
],
118
-
"metrics": [ # List of schema fields grouped as dimensions. These are fields that can be used with an aggregate function such as sum, avg, min, max.
119
+
"metrics": [ # List of schema fields grouped as dimensionsthat can be used with an aggregate function such as `sum`, `avg`, `min`, and `max`.
119
120
{ # Message type for the schema element
120
-
"name": "A String", # Name of the field
121
-
"properties": { # Message type for schema property # Property of the schema field E.g. { "createTime": "2016-02-26T10:23:09.592Z", "custom": "false", "type": "string" }
122
-
"createTime": "A String", # Creation time of the field
123
-
"custom": "A String", # Custom is a flag signifying if the field was provided as part of the standard dataset or a custom field created by the customer
121
+
"name": "A String", # Name of the field.
122
+
"properties": { # Properties for the schema field. # Properties for the schema field. For example: { "createTime": "2016-02-26T10:23:09.592Z", "custom": "false", "type": "string" }
123
+
"createTime": "A String", # Time the field was created in RFC3339 string form. For example: `2016-02-26T10:23:09.592Z`.
124
+
"custom": "A String", # Flag that specifies whether the field is standard in the dataset or a custom field created by the customer. `true` indicates that it is a custom field.
124
125
"type": "A String", # Data type of the field.
0 commit comments