@@ -5,6 +5,12 @@
55 "scopes": {
66 "https://www.googleapis.com/auth/cloud-platform": {
77 "description": "View and manage your data across Google Cloud Platform services"
8+ },
9+ "https://www.googleapis.com/auth/firebase": {
10+ "description": "View and administer all your Firebase data and settings"
11+ },
12+ "https://www.googleapis.com/auth/firebase.readonly": {
13+ "description": "View all your Firebase data and settings"
814 }
915 }
1016 }
@@ -42,7 +48,8 @@
4248 },
4349 "path": "v1/{+name}/rulesets",
4450 "scopes": [
45− "https://www.googleapis.com/auth/cloud-platform"
51+ "https://www.googleapis.com/auth/cloud-platform",
52+ "https://www.googleapis.com/auth/firebase"
4653 ]
4754 },
4855 "get": {
@@ -67,7 +74,9 @@
6774 },
6875 "path": "v1/{+name}",
6976 "scopes": [
70− "https://www.googleapis.com/auth/cloud-platform"
77+ "https://www.googleapis.com/auth/cloud-platform",
78+ "https://www.googleapis.com/auth/firebase",
79+ "https://www.googleapis.com/auth/firebase.readonly"
7180 ]
7281 },
7382 "list": {
@@ -103,7 +112,9 @@
103112 },
104113 "path": "v1/{+name}/rulesets",
105114 "scopes": [
106− "https://www.googleapis.com/auth/cloud-platform"
115+ "https://www.googleapis.com/auth/cloud-platform",
116+ "https://www.googleapis.com/auth/firebase",
117+ "https://www.googleapis.com/auth/firebase.readonly"
107118 ]
108119 },
109120 "delete": {
@@ -128,7 +139,8 @@
128139 },
129140 "path": "v1/{+name}",
130141 "scopes": [
131− "https://www.googleapis.com/auth/cloud-platform"
142+ "https://www.googleapis.com/auth/cloud-platform",
143+ "https://www.googleapis.com/auth/firebase"
132144 ]
133145 }
134146 }
@@ -151,7 +163,7 @@
151163 "httpMethod": "PUT",
152164 "parameters": {
153165 "name": {
154− "description": "Resource name for the `Release`.\n\n`Release` names may be structured `app1/prod/v2` or flat `app1_prod_v2`\nwhich affords developers a great deal of flexibility in mapping the name\nto the style that best fits their existing development practices. For\nexample, a name could refer to an environment, an app, a version, or some\ncombination of three.\n\nIn the table below, for the project name `projects/foo`, the following\nrelative release paths show how flat and structured names might be chosen\nto match a desired development / deployment strategy.\n\nUse Case | Flat Name | Structured Name\n-------------|---------------------|----------------\nEnvironments | releases/qa | releases/qa\nApps | releases/app1_qa | releases/app1/qa\nVersions | releases/app1_v2_qa | releases/app1/v2/qa\n\nThe delimiter between the release name path elements can be almost anything\nand it should work equally well with the release name list filter, but in\nmany ways the structured paths provide a clearer picture of the\nrelationship between `Release` instances.\n\nFormat: `projects/{project_id}/releases/{release_id}`\n",
166+ "description": "Resource name for the `Release`.\n\n`Release` names may be structured `app1/prod/v2` or flat `app1_prod_v2`\nwhich affords developers a great deal of flexibility in mapping the name\nto the style that best fits their existing development practices. For\nexample, a name could refer to an environment, an app, a version, or some\ncombination of three.\n\nIn the table below, for the project name `projects/foo`, the following\nrelative release paths show how flat and structured names might be chosen\nto match a desired development / deployment strategy.\n\nUse Case | Flat Name | Structured Name\n-------------|---------------------|----------------\nEnvironments | releases/qa | releases/qa\nApps | releases/app1_qa | releases/app1/qa\nVersions | releases/app1_v2_qa | releases/app1/v2/qa\n\nThe delimiter between the release name path elements can be almost anything\nand it should work equally well with the release name list filter, but in\nmany ways the structured paths provide a clearer picture of the\nrelationship between `Release` instances.\n\nFormat: `projects/{project_id}/releases/{release_id}`",
155167 "required": true,
156168 "pattern": "^projects/[^/]*/releases/.*$",
157169 "location": "path",
@@ -160,7 +172,8 @@
160172 },
161173 "path": "v1/{+name}",
162174 "scopes": [
163− "https://www.googleapis.com/auth/cloud-platform"
175+ "https://www.googleapis.com/auth/cloud-platform",
176+ "https://www.googleapis.com/auth/firebase"
164177 ]
165178 },
166179 "create": {
@@ -188,7 +201,8 @@
188201 },
189202 "path": "v1/{+name}/releases",
190203 "scopes": [
191− "https://www.googleapis.com/auth/cloud-platform"
204+ "https://www.googleapis.com/auth/cloud-platform",
205+ "https://www.googleapis.com/auth/firebase"
192206 ]
193207 },
194208 "get": {
@@ -199,7 +213,7 @@
199213 "parameterOrder": [
200214 "name"
201215 ],
202− "description": "Get a `Release` by name.\n",
216+ "description": "Get a `Release` by name.",
203217 "flatPath": "v1/projects/{projectsId}/releases/{releasesId}",
204218 "httpMethod": "GET",
205219 "parameters": {
@@ -213,7 +227,9 @@
213227 },
214228 "path": "v1/{+name}",
215229 "scopes": [
216− "https://www.googleapis.com/auth/cloud-platform"
230+ "https://www.googleapis.com/auth/cloud-platform",
231+ "https://www.googleapis.com/auth/firebase",
232+ "https://www.googleapis.com/auth/firebase.readonly"
217233 ]
218234 },
219235 "list": {
@@ -254,7 +270,9 @@
254270 },
255271 "path": "v1/{+name}/releases",
256272 "scopes": [
257− "https://www.googleapis.com/auth/cloud-platform"
273+ "https://www.googleapis.com/auth/cloud-platform",
274+ "https://www.googleapis.com/auth/firebase",
275+ "https://www.googleapis.com/auth/firebase.readonly"
258276 ]
259277 },
260278 "delete": {
@@ -279,7 +297,8 @@
279297 },
280298 "path": "v1/{+name}",
281299 "scopes": [
282− "https://www.googleapis.com/auth/cloud-platform"
300+ "https://www.googleapis.com/auth/cloud-platform",
301+ "https://www.googleapis.com/auth/firebase"
283302 ]
284303 }
285304 }
@@ -311,7 +330,9 @@
311330 },
312331 "path": "v1/{+name}:test",
313332 "scopes": [
314− "https://www.googleapis.com/auth/cloud-platform"
333+ "https://www.googleapis.com/auth/cloud-platform",
334+ "https://www.googleapis.com/auth/firebase",
335+ "https://www.googleapis.com/auth/firebase.readonly"
315336 ]
316337 }
317338 }
@@ -333,7 +354,7 @@
333354 "format": "google-datetime"
334355 },
335356 "name": {
336− "description": "Resource name for the `Release`.\n\n`Release` names may be structured `app1/prod/v2` or flat `app1_prod_v2`\nwhich affords developers a great deal of flexibility in mapping the name\nto the style that best fits their existing development practices. For\nexample, a name could refer to an environment, an app, a version, or some\ncombination of three.\n\nIn the table below, for the project name `projects/foo`, the following\nrelative release paths show how flat and structured names might be chosen\nto match a desired development / deployment strategy.\n\nUse Case | Flat Name | Structured Name\n-------------|---------------------|----------------\nEnvironments | releases/qa | releases/qa\nApps | releases/app1_qa | releases/app1/qa\nVersions | releases/app1_v2_qa | releases/app1/v2/qa\n\nThe delimiter between the release name path elements can be almost anything\nand it should work equally well with the release name list filter, but in\nmany ways the structured paths provide a clearer picture of the\nrelationship between `Release` instances.\n\nFormat: `projects/{project_id}/releases/{release_id}`\n",
357+ "description": "Resource name for the `Release`.\n\n`Release` names may be structured `app1/prod/v2` or flat `app1_prod_v2`\nwhich affords developers a great deal of flexibility in mapping the name\nto the style that best fits their existing development practices. For\nexample, a name could refer to an environment, an app, a version, or some\ncombination of three.\n\nIn the table below, for the project name `projects/foo`, the following\nrelative release paths show how flat and structured names might be chosen\nto match a desired development / deployment strategy.\n\nUse Case | Flat Name | Structured Name\n-------------|---------------------|----------------\nEnvironments | releases/qa | releases/qa\nApps | releases/app1_qa | releases/app1/qa\nVersions | releases/app1_v2_qa | releases/app1/v2/qa\n\nThe delimiter between the release name path elements can be almost anything\nand it should work equally well with the release name list filter, but in\nmany ways the structured paths provide a clearer picture of the\nrelationship between `Release` instances.\n\nFormat: `projects/{project_id}/releases/{release_id}`",
337358 "type": "string"
338359 },
339360 "rulesetName": {
@@ -517,7 +538,7 @@
517538 "id": "Issue"
518539 }
519540 },
520− "revision": "20160513",
541+ "revision": "20160930",
521542 "basePath": "",
522543 "icons": {
523544 "x32": "http://www.google.com/images/icons/product/search-32.gif",
@@ -616,7 +637,7 @@
616637 "location": "query"
617638 }
618639 },
619− "documentationLink": "https://firebase.google.com/docs/storage/security/start",
640+ "documentationLink": "https://firebase.google.com/docs/storage/security",
620641 "ownerDomain": "google.com",
621642 "batchPath": "batch",
622643 "servicePath": "",